How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed 2 days ago
Rank Trend
2026-06-012026-06-03
Activity & Reach
Stars
539
Forks
44
Last Push
2026-06-02
2 days ago
Commits (4 wk)
925
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
19
Rank Change
▼1
was #100
Analysis
HVTrust Dimensions
62.4 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.9 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
13.2 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
6.6 / 20
Activity Inputs
74.1 / 100
StarsRepository reach
16.4 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
7.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
5.5 / 10
via deps.dev · OpenSSF
Signed Commits
100%
of last 100 commits verified
Code-Review0
Maintained0
Dependency-Update-Tool10
Security-Policy10
Dangerous-Workflow0
Binary-Artifacts10
Token-Permissions0
CII-Best-Practices2
Pinned-Dependencies9
Fuzzing10
Vulnerabilities10
License10
SAST9
Packaging10
Branch-Protection-1
Signed-Releases0
CI-Tests10
Contributors6
Is Bernstein safe?
Bernstein 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 Bernstein publish package provenance?
No published build provenance is currently detected for Bernstein. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Bernstein have an OpenSSF Scorecard?
Bernstein has an OpenSSF Scorecard score of 5.5/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 Bernstein actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Bernstein use?
Bernstein ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Bernstein's commits signed?
100% of the last 100 commits to Bernstein 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 Bernstein?
HVTrust scores Bernstein 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
