@atproto-labs/did-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 reflects legitimate CI/CD automation for the bluesky-social/atproto monorepo; SLSA attestation confirms integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by migration to automated GitHub Actions publishing; SLSA provenance attestation rules out account takeover for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): Package is published from the official bluesky-social/atproto monorepo via CI/CD with Sigstore attestation; this is expected and stable for all versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.6 | 6 / 1 | |
| 0.2.5 | 6 / 1 | |
| 0.2.4 | 6 / 1 | |
| 0.2.3 | 6 / 1 | |
| 0.2.2 | 6 / 1 | |
| 0.2.1 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.13 | 6 / 1 |
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
2 findingsThis version was published by a different npm account than previous versions on 2026-01-06. 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.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.