@forge/manifest
20
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
atlassianartifactteam
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian publishes via their own registry; lack of Sigstore provenance is consistent across all their packages. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 13.2.0 | 9 / 5 | |
| 13.1.0 | 9 / 5 | |
| 13.0.0 | 9 / 5 | |
| 12.9.0 | 9 / 5 | |
| 12.8.0 | 9 / 5 | |
| 12.7.0 | 9 / 5 | |
| 12.6.0 | 9 / 5 | |
| 12.5.0 | 9 / 5 | |
| 12.4.0 | 9 / 5 | |
| 12.3.0 | 9 / 5 | |
| 12.2.0 | 9 / 5 | |
| 12.1.1 | 9 / 5 | |
| 12.1.0 | 9 / 5 | |
| 12.0.0 | 9 / 5 | |
| 11.3.2 | 9 / 5 | |
| 11.3.1 | 9 / 5 | |
| 11.3.0 | 9 / 5 | |
| 11.2.0 | 9 / 5 | |
| 11.1.0 | 9 / 5 | |
| 11.0.0 | 9 / 5 |
v13.2.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.