@agentskit/rag
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 | missing-githead | AI (provenance): Single version anomaly with no other malicious signals; package content and diff are clean. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @agentskit/* package; Levenshtein match to 'pg' is coincidental, not a typosquat. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 1 / 6 | |
| 0.4.16 | 1 / 6 | |
| 0.4.14 | 1 / 6 | |
| 0.4.13 | 1 / 4 | |
| 0.4.12 | 1 / 4 | |
| 0.4.11 | 1 / 4 | |
| 0.4.10 | 1 / 4 | |
| 0.4.9 | 1 / 4 | |
| 0.4.8 | 1 / 4 | |
| 0.4.7 | 1 / 4 | |
| 0.4.6 | 1 / 4 | |
| 0.4.5 | 1 / 4 | |
| 0.4.4 | 1 / 4 | |
| 0.4.3 | 1 / 4 | |
| 0.4.2 | 1 / 4 | |
| 0.4.1 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.4 | 1 / 4 | |
| 0.3.3 | 1 / 4 | |
| 0.3.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.1 | 1 / 4 | |
| 0.1.8 | 1 / 4 | |
| 0.1.7 | 1 / 4 | |
| 0.1.6 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 1 / 4 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 |
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.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.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.