@atlaskit/adf-utils
Set of utilities to traverse, modify and create ADF documents.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlaskit packages are published via Atlassian's internal artifact pipeline which does not currently attach Sigstore provenance; this is consistent across all versions and not a risk indicator. | ai |
Versions (showing 5 of 205)
| Version | Deps | Published |
|---|---|---|
| 19.0.4 | 3 / 5 | |
| 19.0.3 | 3 / 5 | |
| 19.0.2 | 3 / 5 | |
| 19.0.1 | 3 / 5 | |
| 19.0.0 | 3 / 6 |
v19.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.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.
v19.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.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.