@atproto/identity
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.5.6 | 2 / 9 | |
| 0.5.5 | 2 / 9 | |
| 0.5.4 | 2 / 9 | |
| 0.5.3 | 2 / 9 | |
| 0.5.2 | 2 / 7 | |
| 0.5.1 | 2 / 7 | |
| 0.5.0 | 2 / 8 | |
| 0.4.12 | 2 / 7 | |
| 0.4.11 | 2 / 7 | |
| 0.4.10 | 2 / 7 | |
| 0.4.9 | 2 / 7 | |
| 0.4.8 | 2 / 7 | |
| 0.4.7 | 2 / 7 | |
| 0.4.6 | 2 / 7 | |
| 0.4.5 | 2 / 7 | |
| 0.4.4 | 2 / 7 | |
| 0.4.3 | 3 / 7 | |
| 0.4.2 | 3 / 6 | |
| 0.4.1 | 3 / 6 |
v0.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.