How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 20:01 UTC·Repo last pushed today
Rank Trend
2026-05-242026-06-04
Activity & Reach
Stars
17.7k
Forks
1.9k
Last Push
2026-06-04
today
Commits (4 wk)
495
Downloads (7d)
19,140
pypi
HN mentions (30d)
—
Open Issues
70
Rank Change
▼7
was #75
Analysis
HVTrust Dimensions
68.0 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
8.3 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.0 / 17
MaintenanceFreshness and commits
20.0 / 20
AdoptionStars and downloads
15.9 / 20
Activity Inputs
90.7 / 100
StarsRepository reach
25.5 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
15.2 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.3 / 10
via deps.dev · OpenSSF
Signed Commits
33%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection6
CI-Tests10
CII-Best-Practices0
Code-Review5
Contributors10
Dangerous-Workflow0
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies0
SAST7
Security-Policy9
Signed-Releases-1
Token-Permissions0
Vulnerabilities0
Is Cognee safe?
Cognee has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Cognee publish package provenance?
No published build provenance is currently detected for Cognee. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cognee have an OpenSSF Scorecard?
Cognee has an OpenSSF Scorecard score of 5.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Cognee actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Cognee use?
Cognee ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cognee's commits signed?
33% of the last 100 commits to Cognee are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Cognee?
HVTrust scores Cognee from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
