Skip to main content
Glama
proof-of-commitment

proof-of-commitment

by piiiico

Prueba de Compromiso

Las estrellas mienten. Las señales de comportamiento no.

Un servidor MCP y una herramienta web que puntúan paquetes de npm, PyPI y repositorios de GitHub según su compromiso de comportamiento: señales que son más difíciles de falsificar que las estrellas, los archivos README o el número de descargas.

El problema de la cadena de suministro

Tres paquetes en un proyecto típico de Node.js son CRÍTICOS en este momento:

  • chalk — 399M de descargas/semana, 1 mantenedor

  • zod — 139M de descargas/semana, 1 mantenedor

  • axios — 96M de descargas/semana, 1 mantenedor (atacado el 1 de abril de 2026)

Las estrellas y la calidad del README no revelan esto. Las señales de comportamiento sí.

Related MCP server: pkgtruth

Pruébalo ahora

Terminal (sin instalación):

npx proof-of-commitment axios zod chalk
# or scan your own project:
npx proof-of-commitment --file package.json
# PyPI too:
npx proof-of-commitment --pypi litellm langchain requests

Demo web (sin instalación): getcommit.dev/audit — pega tus paquetes y obtén puntuaciones de riesgo en segundos.

Servidor MCP (sin instalación):

{
  "mcpServers": {
    "proof-of-commitment": {
      "type": "streamable-http",
      "url": "https://poc-backend.amdal-dev.workers.dev/mcp"
    }
  }
}

Agrégalo a Claude Desktop, Cursor, Windsurf o cualquier herramienta de IA compatible con MCP. Luego pregunta:

"Audita mi package.json en busca de riesgos en la cadena de suministro" "Puntúa axios, zod, chalk, lodash: ¿cuál tiene mayor riesgo?" "¿Está vercel/ai mantenido activamente?"

GitHub Action

Agrega auditoría de la cadena de suministro a cualquier pipeline de CI: detecta automáticamente paquetes desde package.json o requirements.txt, publica los resultados como un comentario en el PR, escribe en el Resumen de Pasos de GitHub y, opcionalmente, falla en paquetes CRÍTICOS.

# .github/workflows/supply-chain-audit.yml
name: Supply Chain Audit
on: [push, pull_request]

jobs:
  audit:
    runs-on: ubuntu-latest
    permissions:
      pull-requests: write   # needed for PR comments
    steps:
      - uses: actions/checkout@v4
      - uses: piiiico/proof-of-commitment@main
        with:
          fail-on-critical: false   # set true to block merges
          comment-on-pr: true       # posts audit table directly on the PR

Cuando comment-on-pr: true (predeterminado), la acción publica automáticamente la tabla de auditoría como un comentario en la solicitud de extracción (pull request) y actualiza el mismo comentario al volver a ejecutarse, para que no recibas spam de comentarios. Los revisores ven la tabla de riesgos sin salir del PR.

Entradas:

Entrada

Predeterminado

Descripción

packages

(auto)

Nombres de paquetes separados por comas (detectados automáticamente desde package.json/requirements.txt si no se establecen)

fail-on-critical

true

Falla el flujo de trabajo si se encuentran paquetes CRÍTICOS

max-packages

20

Máximo de paquetes a auditar al detectar automáticamente

comment-on-pr

true

Publica los resultados de la auditoría como un comentario en el PR (requiere permiso pull-requests: write)

Salidas: has-critical, critical-count, audit-summary (tabla markdown, también escrita en el Resumen de Pasos).

Ejemplo de comentario en PR / salida del Resumen de Pasos:

| Package | Risk        | Score | Maintainers | Downloads/wk | Age   |
|---------|-------------|-------|-------------|--------------|-------|
| chalk   | 🔴 CRITICAL | 75    | 1           | 380M         | 12.7y |
| zod     | 🔴 CRITICAL | 83    | 1           | 133M         | 6.1y  |
| axios   | 🔴 CRITICAL | 89    | 1           | 93M          | 11.6y |

Insignias de README

Agrega una insignia de puntuación de compromiso a cualquier paquete que mantengas o del que dependas:

![commit score](https://poc-backend.amdal-dev.workers.dev/api/badge/npm/YOUR-PACKAGE)

Ejemplos:

Paquete

URL de la insignia

axios

![commit](https://poc-backend.amdal-dev.workers.dev/api/badge/npm/axios)

zod

![commit](https://poc-backend.amdal-dev.workers.dev/api/badge/npm/zod)

litellm

![commit](https://poc-backend.amdal-dev.workers.dev/api/badge/pypi/litellm)

Colores: 🟢 saludable (75+) · 🟡 bueno (60–74) · 🟡 moderado (40–59) · 🟠 alto riesgo (<40) · 🔴 CRÍTICO (un solo mantenedor + >10M de descargas/semana)

Las insignias se almacenan en caché durante 5 minutos en el borde de Cloudflare. No se necesita clave de API.

API REST

Sin clave de API. Sin instalación.

curl https://poc-backend.amdal-dev.workers.dev/api/audit \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"packages": ["axios", "zod", "chalk", "lodash", "express"]}'
{
  "count": 5,
  "results": [
    {
      "name": "chalk",
      "ecosystem": "npm",
      "score": 75,
      "maintainers": 1,
      "weeklyDownloads": 398397580,
      "ageYears": 12.7,
      "trend": "stable",
      "riskFlags": ["CRITICAL"]
    },
    ...
  ]
}

7 herramientas MCP

Herramienta

Descripción

audit_dependencies

Auditoría de riesgo por lotes para hasta 20 paquetes npm/PyPI

lookup_npm_package

Perfil de comportamiento de un solo paquete npm

lookup_pypi_package

Perfil de comportamiento de un solo paquete PyPI

lookup_github_repo

Puntuación de compromiso de repositorio de GitHub (longevidad, frecuencia de confirmación, profundidad de colaboradores)

lookup_business

Registro mercantil noruego: años de operación, empleados, finanzas

lookup_business_by_org

Lo mismo, por número de organización

query_commitment

Datos de comportamiento de la extensión del navegador (visitantes verificados únicos, tasa de repetición)

Qué mide la puntuación

Cada paquete se puntúa de 0 a 100 en:

  • Longevidad — ¿Cuánto tiempo ha existido el paquete? Los paquetes abandonados se reactivan para ataques.

  • Profundidad del mantenedor — Un solo mantenedor + millones de descargas semanales = la superficie de ataque que LiteLLM explotó.

  • Consistencia de lanzamiento — Los lanzamientos regulares señalan una supervisión activa. Largos intervalos = acumulación de vulnerabilidades.

  • Tendencia de descargas — Los paquetes en crecimiento atraen más escrutinio (y ataques). Estable = perfil más bajo.

Indicadores de riesgo:

  • CRÍTICO — un solo mantenedor + >10M de descargas semanales (perfil exacto de ataque de LiteLLM/axios)

  • ALTO — paquete <1 año de antigüedad + adopción rápida

  • ADVERTENCIA — sin lanzamientos en más de 12 meses

Puntos de datos reales

chalk     — score 75, 1 maintainer, 399M/week  ⚑ CRITICAL
zod       — score 83, 1 maintainer, 139M/week  ⚑ CRITICAL
axios     — score 89, 1 maintainer,  96M/week  ⚑ CRITICAL (attacked Apr 1 2026)
lodash    — score 88, 3 maintainers, 68M/week
express   — score 91, 5 maintainers, 35M/week
litellm   — score 74, 1 maintainer           ⚑ CRITICAL (supply chain attack Mar 2026)

Por qué señales de comportamiento

El ataque a LiteLLM (marzo de 2026) y el ataque a axios (abril de 2026) siguieron el mismo patrón: credenciales robadas → paquete malicioso enviado → más de 97M de máquinas expuestas. Ambos paquetes fueron calificados como CRÍTICOS por estas métricas antes de los ataques.

Las señales declarativas (estrellas, calidad del README, insignias de CI) no capturan este riesgo. El compromiso de comportamiento sí.

Listado en el registro oficial de MCP

registry.modelcontextprotocol.io → io.github.piiiico/proof-of-commitment

Stack

Capa

Tecnología

Backend

Cloudflare Workers + D1

MCP

SDK del Protocolo de Contexto de Modelo

Datos

registro npm, PyPI, API de GitHub, Brønnøysund (NO)

Landing

Astro + Cloudflare Pages

La visión más amplia

La auditoría de la cadena de suministro es la primera herramienta. La primitiva subyacente es un grafo de compromiso: señales de comportamiento que reemplazan la confianza basada en el contenido en cualquier dominio.

Cuando el contenido es fácil de falsificar (reseñas, estrellas, READMEs), el compromiso se convierte en la señal. Un mantenedor que ha realizado 847 lanzamientos durante 12 años es un tipo de compromiso diferente al de alguien que publicó una vez en 2023.

La misma lógica se aplica a sitios web, empresas y agentes de IA. Dos redes de tarjetas han nombrado independientemente esta brecha: Mastercard Verifiable Intent §9.2 enumera explícitamente la confianza conductual como "no cubierta". Visa TAP identifica agentes sin responder si se debe confiar en ellos.

La Prueba de Compromiso es la capa de confianza a la que apuntan.

→ getcommit.dev

Ejecutar localmente

bun install
bun run dev:backend     # local server with SQLite
bun run test:e2e        # E2E test with mock World ID

Desplegar:

bun run deploy          # deploys to Cloudflare Workers

Available Tools

8 tools
audit_dependenciesAInspect

Batch-score multiple npm or PyPI packages for supply chain risk. Takes a list of package names and returns a risk table sorted by commitment score (lowest = highest risk first).

Risk flags:

  • CRITICAL: single npm publisher + >10M weekly downloads (publish-access concentration risk)

  • HIGH: new package (<1yr) + high downloads (unproven, rapid adoption = supply chain risk)

  • WARN: no release in 12+ months (potential abandonware)

  • WARN: dormant publishers with current scope access — contributors who stopped publishing but retain npm tokens (the Mastra incident vector, June 2026)

Perfect for auditing a full package.json or requirements.txt — paste your dependency list and get a prioritized risk report.

Examples: score all deps in a project, compare two similar packages, identify abandonware before it becomes a CVE.

Inputs: packages (required), ecosystem.

lookup_businessBInspect

Search for a Norwegian business and get its commitment profile from public data (Brønnøysund Register Centre). Returns real commitment signals that can't be faked:

  • Temporal commitment: how long the business has operated

  • Financial commitment: revenue, profitability, equity health

  • Operational commitment: employee count, active status

  • Overall commitment score (0-100)

Data source: Norwegian government registers (Brreg). No user-contributed data needed — immediate trust verification for any Norwegian business.

Inputs: query (required), maxResults.

lookup_business_by_orgAInspect

Look up a specific Norwegian business by organization number and get its commitment profile from public data (Brønnøysund Register Centre). Returns real commitment signals: longevity, financial health, operational activity, and overall commitment score.

Inputs: orgNumber (required).

lookup_github_repoAInspect

Get a behavioral commitment profile for any public GitHub repository. Returns real signals: how long the project has existed, recent commit frequency, contributor community size, release cadence, and social proof. These are behavioral commitments — harder to fake than README claims.

Useful for: vetting open-source dependencies, evaluating AI tools/frameworks, assessing vendor reliability. Examples: "vercel/next.js", "facebook/react", "https://github.com/piiiico/proof-of-commitment"

Inputs: repo (required).

lookup_go_moduleAInspect

Get a behavioral commitment profile for any Go module on proxy.golang.org. Takes a full module path (e.g., "github.com/gin-gonic/gin", "golang.org/x/net", "k8s.io/client-go", "gopkg.in/yaml.v3") and returns real signals: module age, version count, publish cadence, GitHub contributors (the closest equivalent to "publishers" since Go has no centralized publisher concept — git push access is the publish equivalent), GitHub stars, OpenSSF Scorecard score.

The Go ecosystem has no centralized download counter, so this profile is GitHub-primary — the linked source repository's activity, contributor count, and Scorecard carry more weight than for npm/PyPI/Cargo. Stars are used as the popularity proxy.

Useful for: vetting Go dependencies before adding to go.mod, identifying abandonware, supply chain risk assessment. Examples: "github.com/gin-gonic/gin", "golang.org/x/crypto", "github.com/spf13/cobra", "k8s.io/api"

Inputs: module (required).

lookup_npm_packageAInspect

Get a behavioral commitment profile for any npm package. Returns real signals: package age, download volume and trend (growing/stable/declining), release consistency, npm publisher count, GitHub contributor count, and linked GitHub activity.

Also returns publisherLifecycle — cross-referencing current maintainers against per-version publish history to flag dormant publishers who still hold npm scope access. The Mastra incident (June 2026) exploited exactly this: a contributor dormant since 2024 with never-revoked scope access.

Supply chain attacks target packages with low publisher depth (few people with npm publish access). Behavioral signals reveal what download counts hide.

Useful for: vetting dependencies, identifying abandonware, due diligence on open-source packages. Examples: "langchain", "@anthropic-ai/sdk", "express", "litellm"

Inputs: package (required).

lookup_pypi_packageAInspect

Get a behavioral commitment profile for any PyPI (Python) package. Returns real signals: package age, download volume and trend, release consistency, publisher/owner count, and linked GitHub activity.

Supply chain attacks target Python packages — LiteLLM (97M downloads/mo) was compromised via stolen PyPI token in March 2026. Behavioral signals reveal what star counts hide.

Useful for: vetting Python dependencies, identifying abandonware, supply chain risk due diligence. Examples: "langchain", "litellm", "openai", "anthropic", "requests", "fastapi", "pydantic"

Inputs: package (required).

query_commitmentAInspect

Query verified behavioral commitment data for a domain. Returns aggregated signals: unique verified visitors, repeat visit rate, and average time spent. These prove real human engagement — harder to fake than reviews or content.

Inputs: domain (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessMostly unanswered

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Deterministic supply-chain provenance, SBOM/AI-BOM generation, and dependency risk analysis for npm and PyPI packages, with 14 security rules and verifiable reports.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      3
      67 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Scores 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.
      3
      67 npm
      1
      Apache 2.0