@agentskit/memory
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 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.11.4 | 1 / 8 | |
| 0.11.3 | 1 / 8 | |
| 0.11.2 | 1 / 8 | |
| 0.11.0 | 1 / 8 | |
| 0.10.13 | 1 / 8 | |
| 0.10.12 | 1 / 8 | |
| 0.10.11 | 1 / 8 | |
| 0.10.10 | 1 / 8 | |
| 0.10.9 | 1 / 8 | |
| 0.10.8 | 1 / 8 | |
| 0.10.7 | 1 / 8 | |
| 0.10.6 | 1 / 8 | |
| 0.10.5 | 1 / 8 | |
| 0.10.4 | 1 / 8 | |
| 0.10.3 | 1 / 8 | |
| 0.10.2 | 1 / 8 | |
| 0.10.1 | 1 / 8 | |
| 0.10.0 | 1 / 8 | |
| 0.9.0 | 1 / 8 | |
| 0.8.3 | 1 / 8 | |
| 0.8.0 | 1 / 8 | |
| 0.5.3 | 1 / 8 | |
| 0.5.1 | 1 / 8 | |
| 0.5.0 | 1 / 8 | |
| 0.4.2 | 1 / 8 | |
| 0.4.0 | 1 / 8 |
v0.11.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.2
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.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.