@forge/storage-data-recovery
Forge Storage Data Recovery SDK
20
Versions
SEE LICENSE IN LICENSE.txt
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; provenance absence is consistent across their entire @forge/* ecosystem. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 2 / 2 | |
| 3.0.0 | 2 / 2 | |
| 2.0.17 | 2 / 1 | |
| 2.0.16 | 2 / 1 | |
| 2.0.15 | 2 / 1 | |
| 2.0.14 | 2 / 1 | |
| 2.0.13 | 2 / 1 | |
| 2.0.12 | 2 / 1 | |
| 2.0.11 | 2 / 1 | |
| 2.0.10 | 2 / 1 | |
| 2.0.9 | 2 / 1 | |
| 2.0.8 | 2 / 1 | |
| 2.0.7 | 2 / 1 | |
| 2.0.6 | 2 / 1 | |
| 2.0.5 | 2 / 1 | |
| 2.0.4 | 2 / 1 | |
| 2.0.3 | 2 / 1 | |
| 2.0.2 | 2 / 1 | |
| 2.0.1 | 2 / 1 | |
| 2.0.0 | 2 / 1 |
v3.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.