proof-of-commitment
Related Servers
Alternatives to proof-of-commitment
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceScores npm packages, PyPI packages and GitHub repositories 0-100 with an A-F grade and plain-language risks. Scans package.json, requirements.txt and lock files; no API key needed.362 npm1Apache 2.0

EVIDIQ Lineageofficial
AlicenseNot gradedqualityBmaintenanceDeterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis for npm and PyPI packages, with 14 security rules and verifiable reports.1MIT- AlicenseAqualityCmaintenanceEnables AI agents and developers to score npm packages, PyPI packages, and GitHub repositories for maintenance health, producing A–F grades, per-signal details, and plain-language risk lists before adoption. It supports checking individual packages, scanning manifests or lock files for transitive dependencies, and comparing alternatives.362 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes an assess_repo tool that scans a repository, local folder, or npm/PyPI package and returns supply-chain risk findings with file, line, and code evidence — install-time scripts, dangerous patterns, secrets, AI-agent manipulation, impersonation and published-artifact mismatches — while never executing the target's code. Findings carry severities from info to critical so results can gate installs and CI jobs.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.1,348 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents and CI to vet npm dependencies before they reach the lockfile, flagging hallucinated, slopsquatted, or otherwise risky packages with evidence-backed verdicts.367 npm4MIT
TDQS
Scored across 8 tools
The package-ecosystem lookups (npm, PyPI, Go, GitHub) are clearly scoped to distinct registries, and audit_dependencies is obviously batch-oriented. The only real overlap is lookup_business vs lookup_business_by_org, which differ mainly by input (name search vs org number), and query_commitment's domain-based scope is somewhat fuzzy against the package lookups since package profiles also aggregate engagement signals.
All eight tools use snake_case verb_noun form, with six sharing a lookup_ prefix and the rest using query_/audit_ verbs appropriately. Minor inconsistency in the noun portion of the lookup family (github_repo vs go_module vs pypi_package vs npm_package vs business), but the pattern remains predictable.
Eight tools is well inside the sweet spot for a registry/commitment-scoring server. Each tool maps to a distinct data source or aggregation mode, and none feels redundant padding.
The surface covers Norwegian business data, four code-ecosystem sources, domain engagement, and batch risk auditing — a coherent lifecycle from single lookup to prioritized audit. Gaps remain: audit_dependencies only handles npm/PyPI (not Go/GitHub), and other major ecosystems (Cargo, RubyGems, Maven) have no lookup at all, but agents can work around these.