@atlaskit/editor-json-transformer
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian's atlassianartifactteam publisher has 98 approved packages; lack of provenance is consistent across their entire catalog and not a meaningful risk signal for this established package. | ai | |
| dependencies | unvetted-dep:@atlaskit/adf-utils | AI (dependencies): @atlaskit/adf-utils is a first-party Atlassian package, expected dependency for this editor transformer. | ai | |
| dependencies | unvetted-dep:@atlaskit/adf-schema | AI (dependencies): @atlaskit/adf-schema is a first-party Atlassian package, expected dependency for this editor transformer. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): @atlaskit/editor-prosemirror is a first-party Atlassian package, expected dependency for this editor transformer. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 8.33.0 | 5 / 3 | |
| 8.32.0 | 5 / 3 | |
| 8.31.8 | 5 / 2 | |
| 8.31.7 | 5 / 2 | |
| 8.31.6 | 5 / 2 | |
| 8.31.5 | 5 / 2 | |
| 8.31.4 | 5 / 1 | |
| 8.31.3 | 5 / 1 | |
| 8.31.2 | 5 / 1 | |
| 8.31.1 | 5 / 1 | |
| 8.31.0 | 5 / 1 | |
| 8.30.0 | 5 / 1 | |
| 8.29.1 | 5 / 1 | |
| 8.29.0 | 5 / 1 | |
| 8.28.0 | 5 / 1 | |
| 8.27.2 | 5 / 1 | |
| 8.27.1 | 5 / 1 | |
| 8.27.0 | 5 / 1 | |
| 8.26.1 | 5 / 1 | |
| 8.26.0 | 5 / 1 | |
| 8.25.1 | 5 / 2 | |
| 8.25.0 | 5 / 2 | |
| 8.24.5 | 5 / 2 | |
| 8.24.4 | 5 / 2 | |
| 8.24.3 | 5 / 2 |
v8.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.31.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.31.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.31.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.31.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.
v8.31.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.