Mar 5, 2026 at 8:12 AM6 signals analysedNo manual reviews · fully automated Trust Signal Breakdownmedium23 sub-signals across 6 dimensions
CVEs, dependency health, and supply chain integrity
2 of 3 sub-signals with data
Known CVEs57%5.0
No known CVEs
via OSV.dev
Dependency Healthno data—
Weight redistributed to sub-signals with data
Supply Chain43%5.0
Supply chain analyzed, no transitive CVEs
via npm provenance
Uptime, latency, error rates, and incident history
4 of 4 sub-signals with data
Uptime35%5.0
100.00% over 6 checks
via Health checks
Response Latency25%3.0
p99: 634ms, p50: 384ms
via Health checks
Error Rate20%1.0
100.00% error rate (6/6)
via Health checks
Incident History20%4.0
1 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
0 of 4 sub-signals with data
Download Volumeno data—
Weight redistributed to sub-signals with data
GitHub Starsno data—
Weight redistributed to sub-signals with data
Dependent Packagesno data—
Weight redistributed to sub-signals with data
Growth Trendno data—
Weight redistributed to sub-signals with data
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
4 of 4 sub-signals with data
Track Record30%1.0
Internal: 1.0 (0 services), External: 1.0 (9 followers, 8 stars)
via Fabric index
Org Maturity30%4.5
Organization, 4.1 years old
via GitHub
Community Standing20%3.0
11 public repositories
via GitHub
Cross-Platform20%3.0
Present on 2 platform(s): github, npm
via Registry scan
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
MCP server with Ollama + Vectra for semantic memory and RAG operations
Package Availability (30d)
100.00%
p50: 384ms · p99: 634ms
Avg Latency
383ms
averaged across 30d health checks
Weekly Downloads
—
no package registry data
Incidents & Alertslast 90 days
Score History14 snapshots
Feb 22Mar 5
Supply Chain & Dependenciestrust chain
Showing 4 of 4 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
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
