@forge/notification
Forge Notification SDK
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Atlassian @forge/* packages are intentionally minimal SDK stubs published by atlassianartifactteam; low-value signals are false positives for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes to their own registry; provenance attestation not expected for this publisher. | ai | |
| dependencies | unvetted-dep:@forge/api | AI (dependencies): @forge/api is a first-party Atlassian Forge SDK package; stable false positive for this package family. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.3.8 | 1 / 3 | |
| 0.3.7 | 1 / 3 | |
| 0.3.6 | 2 / 4 | |
| 0.3.5 | 2 / 4 | |
| 0.3.4 | 2 / 4 | |
| 0.3.3 | 2 / 4 | |
| 0.3.2 | 2 / 4 | |
| 0.3.1 | 2 / 4 | |
| 0.3.0 | 2 / 4 | |
| 0.2.2 | 2 / 4 | |
| 0.2.1 | 2 / 4 | |
| 0.2.0 | 2 / 4 | |
| 0.1.0 | 2 / 4 | |
| 0.0.2 | 0 / 0 |
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
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.2.2
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.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
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.0
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.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.