@atproto-labs/xrpc-utils
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing for bluesky-social/atproto monorepo; backed by SLSA provenance attestation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer removal consistent with org-level CI/CD publishing migration for the atproto monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD migration is a known pattern for monorepo packages; SLSA attestation confirms legitimate origin. | ai | |
| provenance | no-provenance | AI (provenance): Official atproto monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.1.0 | 2 / 1 | |
| 0.0.24 | 2 / 1 | |
| 0.0.23 | 2 / 1 | |
| 0.0.22 | 2 / 1 | |
| 0.0.21 | 2 / 1 | |
| 0.0.20 | 2 / 1 | |
| 0.0.19 | 2 / 1 | |
| 0.0.18 | 2 / 1 | |
| 0.0.17 | 2 / 1 | |
| 0.0.16 | 2 / 1 | |
| 0.0.15 | 2 / 1 |
v0.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.