@atproto/common
Shared web-platform-friendly code for atproto libraries
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 | missing-githead | AI (provenance): Minor CI metadata gap, no behavioral signal; publisher has long clean history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Deps are official sibling package and established cbor lib, not suspicious. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing, confirmed by SLSA provenance attestation from bluesky-social/atproto. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI/CD migration; SLSA attestation confirms legitimate automated publish pipeline. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used for HTTP Basic Auth token handling in obfuscate.ts — legitimate, stable pattern for this package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 0.7.2 | 5 / 2 | |
| 0.7.1 | 5 / 2 | |
| 0.7.0 | 5 / 2 | |
| 0.6.5 | 5 / 2 | |
| 0.6.4 | 5 / 2 | |
| 0.6.3 | 5 / 2 | |
| 0.6.2 | 5 / 3 | |
| 0.6.1 | 5 / 3 | |
| 0.6.0 | 5 / 3 | |
| 0.5.16 | 5 / 3 | |
| 0.5.15 | 5 / 3 | |
| 0.5.14 | 5 / 3 | |
| 0.5.13 | 6 / 3 | |
| 0.5.12 | 6 / 3 | |
| 0.5.11 | 6 / 3 | |
| 0.5.10 | 6 / 3 | |
| 0.5.9 | 6 / 3 | |
| 0.5.8 | 6 / 3 | |
| 0.5.7 | 6 / 3 | |
| 0.5.6 | 6 / 3 | |
| 0.5.5 | 6 / 3 | |
| 0.5.4 | 6 / 3 | |
| 0.5.3 | 6 / 3 | |
| 0.5.2 | 6 / 3 | |
| 0.5.1 | 6 / 3 | |
| 0.5.0 | 6 / 3 | |
| 0.4.12 | 6 / 3 | |
| 0.4.11 | 6 / 3 | |
| 0.4.10 | 6 / 3 | |
| 0.4.9 | 6 / 3 | |
| 0.4.8 | 6 / 3 | |
| 0.4.7 | 6 / 3 | |
| 0.4.6 | 6 / 3 | |
| 0.4.5 | 6 / 3 | |
| 0.4.4 | 6 / 3 | |
| 0.4.3 | 6 / 3 | |
| 0.4.2 | 6 / 3 | |
| 0.4.1 | 6 / 3 | |
| 0.3.0 | 5 / 0 | |
| 0.1.1 | 4 / 0 | |
| 0.1.0 | 4 / 0 | |
| 0.0.1 | 4 / 0 |
v0.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dholms.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsThis version was published by a different npm account (dholms) than the most recent previously approved version (pfrazee) on 2023-03-01. It has since remained available on npm for 1242 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
2 findingsThis version was published by a different npm account (dholms) than the most recent previously approved version (pfrazee) on 2023-02-22. It has since remained available on npm for 1249 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.