@atproto/jwk-webcrypto
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-added | AI (maintainer-change): matthieu-bluesky is a Bluesky org contributor; consistent with org-level maintainer management. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a declared dependency used transitively via @atproto/jwk; not a security concern for this ATProto ecosystem package. | ai | |
| provenance | no-provenance | AI (provenance): Established ATProto monorepo package from a trusted publisher; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 3 / 1 | |
| 0.2.0 | 3 / 1 | |
| 0.1.10 | 3 / 1 | |
| 0.1.9 | 3 / 1 | |
| 0.1.8 | 3 / 1 | |
| 0.1.7 | 3 / 1 |
v0.3.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.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.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.