How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-22 00:01 UTC·Repo last pushed 2 days ago
Rank Trend
2026-06-192026-06-21
Activity & Reach
Stars
99
Forks
11
Last Push
2026-06-20
2 days ago
Commits (4 wk)
155
Downloads (7d)
646
npm+pypi
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #36
Analysis
HVTrust Dimensions
82.2 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
20.8 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
15.0 / 17
MaintenanceFreshness and commits
19.9 / 20
AdoptionStars and downloads
8.5 / 20
Activity Inputs
66.9 / 100
StarsRepository reach
12.0 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
5.0 / 20
Supply Chain Trust
Package Provenance
Verified
npm attestation
OSSF Scorecard
7.7 / 10
OpenSSF Scorecard · scanned Jun 21, 2026
Signed Commits
74%
of last 100 commits verified
Binary-Artifacts10
Branch-Protection3
CI-Tests10
CII-Best-Practices5
Code-Review8
Contributors3
Dangerous-Workflow10
Dependency-Update-Tool10
Fuzzing0
License10
Maintained10
Packaging10
Pinned-Dependencies7
SAST10
Security-Policy10
Signed-Releases10
Token-Permissions10
Vulnerabilities0
Is Threadplane safe?
Public supply-chain signals for Threadplane are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Threadplane carries less obvious unverified-evidence risk than projects with thin signals.
Does Threadplane publish package provenance?
Yes. Threadplane's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Threadplane have an OpenSSF Scorecard?
Threadplane has an OpenSSF Scorecard score of 7.7/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 Threadplane actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Threadplane use?
Threadplane ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Threadplane's commits signed?
74% of the last 100 commits to Threadplane 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.
AI agent surface
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Anthropic
Postgres
Redis
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
3 tags
Broad capability areas detected.
browser
code
database
Detailed evidence is not shown in the public view.
Package Provenance Drift
medium confidence
Partial
Some package metadata matches; some source metadata is missing
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Threadplane?
HVTrust scores Threadplane 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.
