@atlassian/atlassian-oauth2
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
atlassianartifactteam
Keywords
atlassianoauth
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:request | AI (dependencies): Standard HTTP client dependency; expected for an OAuth2 library from Atlassian. | ai | |
| dependencies | unvetted-dep:atlassian-jwt | AI (dependencies): First-party Atlassian JWT library; expected dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian org package published via their own registry; provenance absence is consistent across their packages. | ai |
v0.9.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.