@agentskit/adapters
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Common for new packages; no other risk signals present to elevate this. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.14.0 | 1 / 7 | |
| 0.13.16 | 1 / 7 | |
| 0.13.13 | 1 / 7 | |
| 0.13.12 | 1 / 7 | |
| 0.13.11 | 1 / 7 | |
| 0.13.10 | 1 / 7 | |
| 0.13.9 | 1 / 7 | |
| 0.13.8 | 1 / 7 | |
| 0.13.7 | 1 / 7 | |
| 0.13.6 | 1 / 7 | |
| 0.13.5 | 1 / 7 | |
| 0.13.4 | 1 / 7 | |
| 0.13.3 | 1 / 7 | |
| 0.13.2 | 1 / 7 | |
| 0.13.0 | 1 / 7 | |
| 0.12.2 | 1 / 5 | |
| 0.12.0 | 1 / 5 | |
| 0.11.0 | 1 / 5 | |
| 0.10.0 | 1 / 5 | |
| 0.9.1 | 1 / 5 | |
| 0.7.1 | 1 / 5 | |
| 0.7.0 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.2 | 1 / 5 | |
| 0.5.1 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.2 | 1 / 5 | |
| 0.4.0 | 1 / 4 |
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.16
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (emersonbraun) on 2026-07-20, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.13.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.