By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Package provenance and scorecards

Many agents and MCP servers ship through npm and PyPI, so classic supply chain controls still apply. Provenance attestations, Sigstore signatures, SLSA levels and OpenSSF Scorecard results help you decide which packages to trust. None of them inspect prompts or tool descriptions, so combine them with agent specific scanning.

Read in this order

  1. Officialnpm: Generating provenance statementsStart here: how npm provenance links a package to its build.
  2. OfficialSLSA: Supply-chain Levels for Software ArtifactsThe SLSA levels, for judging how trustworthy a build process is.
  3. Open sourceOpenSSF ScorecardAutomated checks you can run to score a dependency's practices.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.