@atproto/oauth-client-browser
ATPROTO OAuth client for the browser (relies on WebCrypto & Indexed DB)
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/CD publishing is confirmed by SLSA provenance attestation; stable for this package going forward. | ai | |
| phantom-deps | phantom-dep:@atproto/jwk | AI (phantom-deps): Same-org @atproto scope; likely used transitively or in type declarations, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@atproto-labs/did-resolver | AI (phantom-deps): Referenced in config files per finding; same-org scope, stable false positive. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 9 / 1 | |
| 0.3.42 | 9 / 1 | |
| 0.3.41 | 9 / 1 | |
| 0.3.40 | 9 / 1 | |
| 0.3.39 | 9 / 1 | |
| 0.3.38 | 9 / 1 | |
| 0.3.37 | 9 / 1 | |
| 0.3.36 | 9 / 1 | |
| 0.3.35 | 9 / 1 | |
| 0.3.34 | 9 / 1 | |
| 0.3.33 | 9 / 1 | |
| 0.3.32 | 8 / 1 | |
| 0.3.31 | 8 / 1 | |
| 0.3.30 | 8 / 1 | |
| 0.3.29 | 8 / 1 | |
| 0.3.28 | 8 / 1 | |
| 0.3.27 | 8 / 1 | |
| 0.3.26 | 8 / 1 | |
| 0.3.25 | 8 / 1 | |
| 0.3.24 | 8 / 1 | |
| 0.3.23 | 8 / 1 | |
| 0.3.22 | 8 / 1 | |
| 0.3.21 | 8 / 1 | |
| 0.3.20 | 8 / 1 | |
| 0.3.19 | 8 / 1 | |
| 0.3.18 | 8 / 1 | |
| 0.3.17 | 8 / 1 | |
| 0.3.16 | 8 / 1 |
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.42
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.41
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. 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.3.40
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. 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.3.39
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.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.