@atproto-labs/handle-resolver
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 consistent with the bluesky-social/atproto monorepo adopting automated CI/CD publishing, confirmed by SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by GitHub Actions publishing is consistent with a monorepo CI migration, not account takeover. SLSA attestation validates the build origin. | ai | |
| dependencies | unvetted-dep:@atproto/did | AI (dependencies): First-party sibling package from the bluesky-social/atproto monorepo; unvetted status reflects review queue lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@atproto-labs/simple-store | AI (dependencies): First-party sibling package from the bluesky-social/atproto monorepo; unvetted status reflects review queue lag, not a security concern. | ai | |
| dependencies | unvetted-dep:@atproto-labs/simple-store-memory | AI (dependencies): First-party sibling package from the bluesky-social/atproto monorepo; unvetted status reflects review queue lag, not a security concern. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 4 / 1 | |
| 0.4.0 | 4 / 1 | |
| 0.3.6 | 4 / 1 | |
| 0.3.5 | 4 / 1 | |
| 0.3.4 | 4 / 1 | |
| 0.3.3 | 4 / 1 | |
| 0.3.2 | 4 / 1 | |
| 0.3.1 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.0 | 4 / 1 |
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.