Mar 4, 2026 at 2:06 AM6 signals analysedNo manual reviews · fully automated Trust Signal Breakdownmedium23 sub-signals across 6 dimensions
CVEs, dependency health, and supply chain integrity
3 of 3 sub-signals with data
Known CVEs40%5.0
No known CVEs
via OSV.dev
Dependency Health30%4.0
30 dependencies (low)
via npm / PyPI
Supply Chain30%4.8
13 transitive CVEs found (penalty: -0.25)
via npm provenance
Uptime, latency, error rates, and incident history
4 of 4 sub-signals with data
Uptime35%5.0
100.00% over 10 checks
via Health checks
Response Latency25%3.0
p99: 597ms, p50: 386ms
via Health checks
Error Rate20%5.0
0.00% error rate (0/10)
via Health checks
Incident History20%3.0
2 incidents in last 90 days
via Incidents table
Commit recency, release cadence, issue response, CI/CD
0 of 4 sub-signals with data
Commit Recencyno data—
Weight redistributed to sub-signals with data
Release Cadenceno data—
Weight redistributed to sub-signals with data
Issue Responseno data—
Weight redistributed to sub-signals with data
CI/CD Presenceno data—
Weight redistributed to sub-signals with data
Downloads, stars, dependents, and growth trajectory
2 of 4 sub-signals with data
Download Volume67%2.0
815 weekly downloads
via npm / PyPI
GitHub Starsno data—
Weight redistributed to sub-signals with data
Dependent Packagesno data—
Weight redistributed to sub-signals with data
Growth Trend33%5.0
+31.9% week-over-week
via npm
License, documentation, security policy, changelog
0 of 4 sub-signals with data
Open Sourceno data—
Weight redistributed to sub-signals with data
Documentationno data—
Weight redistributed to sub-signals with data
Security Policyno data—
Weight redistributed to sub-signals with data
Changelogno data—
Weight redistributed to sub-signals with data
Track record, org maturity, community standing
0 of 4 sub-signals with data
Track Recordno data—
Weight redistributed to sub-signals with data
Org Maturityno data—
Weight redistributed to sub-signals with data
Community Standingno data—
Weight redistributed to sub-signals with data
Cross-Platformno data—
Weight redistributed to sub-signals with data
Limited data available — 3 of 6 signals pending evaluation
About this score
Scored across 23 sub-signals in 6 dimensionsScoring engine v1 (beta) — actively being expandedPhase 1: Core sub-signal architecture (live)Phase 2: Permission scope & expanded collection (in progress)
Trust AssessmentAI Assessment
Run AI models locally on your machine with node.js bindings for llama.cpp. Enforce a JSON schema on the model output on the generation level
Package Availability (30d)
100.00%
p50: 386ms · p99: 597ms
Avg Latency
315ms
averaged across 30d health checks
Weekly Downloads
815+32%
npm weekly
Incidents & Alertslast 90 days
Score History17 snapshots
Feb 22Mar 4
Community & Ecosystemadoption signals
Supply Chain & Dependenciestrust chain
Showing 6 of 30 dependencies Data Sources6 indexed
◎
OSV.devCVE database · vulnerability scanning for npm & PyPI packages
◈
GitHub APICommits, issues, releases, repo metadata, transparency checks
⬡
npm RegistryPackage metadata, weekly downloads, maintainers, dependencies
⬡
PyPIPackage metadata, weekly downloads, dependency tree
△
HTTP Health Checks15-min pings · uptime, latency, status monitoring
◎
PyPI StatsDownload statistics and trends
Version History
VERSIONRELEASED
Showing 6 of 10 releases Are you the publisher?
Claim this profile to unlock deeper evaluation, real-time monitoring,
and trust signals that help agents discover your service.
Share this Trust Score
Generate a scorecard image optimised for X, LinkedIn and other social platforms.
⬇ Download Score Card
