@atproto/xrpc-server
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 from devinivy to GitHub Actions is a legitimate CI/CD migration, confirmed by SLSA provenance attestation on the atproto monorepo. | ai | |
| dependencies | unvetted-dep:@atproto/ws-client | AI (dependencies): First-party sibling package in the bluesky-social/atproto monorepo; stable false positive for this package. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 0.11.11 | 15 / 14 | |
| 0.11.10 | 15 / 14 | |
| 0.11.9 | 15 / 14 | |
| 0.11.8 | 15 / 14 | |
| 0.11.7 | 15 / 14 | |
| 0.11.6 | 15 / 14 | |
| 0.11.5 | 15 / 14 | |
| 0.11.4 | 15 / 14 | |
| 0.11.3 | 15 / 14 | |
| 0.11.2 | 15 / 14 | |
| 0.11.1 | 15 / 15 | |
| 0.11.0 | 15 / 15 | |
| 0.10.22 | 15 / 14 | |
| 0.10.21 | 15 / 14 | |
| 0.10.20 | 15 / 14 | |
| 0.10.19 | 15 / 14 | |
| 0.10.18 | 15 / 14 | |
| 0.10.17 | 15 / 14 | |
| 0.10.16 | 15 / 14 | |
| 0.10.15 | 15 / 14 | |
| 0.10.14 | 13 / 12 | |
| 0.10.13 | 13 / 12 | |
| 0.10.12 | 13 / 12 | |
| 0.10.11 | 13 / 12 | |
| 0.10.10 | 13 / 12 | |
| 0.10.9 | 13 / 12 | |
| 0.10.8 | 13 / 12 | |
| 0.10.7 | 13 / 12 | |
| 0.10.6 | 13 / 12 | |
| 0.10.5 | 13 / 12 | |
| 0.10.4 | 13 / 12 | |
| 0.10.3 | 13 / 12 | |
| 0.10.2 | 13 / 12 | |
| 0.10.1 | 13 / 12 | |
| 0.10.0 | 13 / 12 | |
| 0.9.6 | 13 / 12 | |
| 0.9.5 | 12 / 12 | |
| 0.9.4 | 12 / 12 | |
| 0.9.3 | 12 / 12 | |
| 0.9.2 | 12 / 12 | |
| 0.9.1 | 12 / 12 | |
| 0.9.0 | 12 / 12 | |
| 0.8.0 | 12 / 11 | |
| 0.7.19 | 12 / 11 | |
| 0.7.18 | 12 / 11 | |
| 0.7.17 | 12 / 11 | |
| 0.7.16 | 12 / 11 | |
| 0.7.15 | 12 / 11 | |
| 0.7.14 | 12 / 11 | |
| 0.7.13 | 12 / 11 | |
| 0.7.12 | 12 / 11 | |
| 0.7.11 | 12 / 11 | |
| 0.7.10 | 12 / 11 | |
| 0.7.9 | 12 / 11 | |
| 0.7.8 | 12 / 11 | |
| 0.7.7 | 12 / 11 | |
| 0.7.6 | 12 / 11 | |
| 0.7.5 | 12 / 11 | |
| 0.7.4 | 12 / 11 | |
| 0.7.3 | 12 / 11 | |
| 0.7.2 | 12 / 11 | |
| 0.7.1 | 12 / 10 | |
| 0.7.0 | 12 / 10 | |
| 0.6.4 | 12 / 10 | |
| 0.6.3 | 12 / 10 | |
| 0.6.2 | 12 / 10 | |
| 0.6.1 | 12 / 10 | |
| 0.6.0 | 12 / 10 | |
| 0.5.3 | 12 / 10 | |
| 0.5.2 | 12 / 10 |
v0.11.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.