@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, 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 | publisher-changed | AI (provenance): Publisher change reflects Atlassian's migration to atlassianartifactteam; stable for this package family. | ai | |
| provenance | missing-githead | AI (provenance): Changed publish environment due to org migration; no malicious signal given the publisher's track record. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Atlassian org restructure; atlaskit-user confirmed as known maintainer by email match on prior approved versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Atlassian org accounts; legitimate org-level publisher migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old atlaskit account replaced by org accounts; consistent with Atlassian's known migration pattern. | 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/adf-utils | AI (dependencies): @atlaskit/adf-utils 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 | |
| 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 |
Versions (showing 42 of 142)
| Version | Deps | Published |
|---|---|---|
| 8.10.1 | 4 / 12 | |
| 8.10.0 | 4 / 12 | |
| 8.9.6 | 4 / 12 | |
| 8.9.5 | 4 / 14 | |
| 8.9.4 | 4 / 14 | |
| 8.9.3 | 5 / 16 | |
| 8.9.2 | 5 / 16 | |
| 8.9.1 | 5 / 16 | |
| 8.9.0 | 5 / 16 | |
| 8.8.5 | 5 / 16 | |
| 8.8.4 | 5 / 16 | |
| 8.8.3 | 5 / 17 | |
| 8.8.2 | 5 / 17 | |
| 8.8.1 | 5 / 17 | |
| 8.8.0 | 5 / 17 | |
| 8.7.7 | 5 / 17 | |
| 8.7.6 | 5 / 17 | |
| 8.7.5 | 5 / 16 | |
| 8.7.4 | 5 / 16 | |
| 8.7.3 | 5 / 16 | |
| 8.7.2 | 5 / 16 | |
| 8.7.1 | 5 / 16 | |
| 8.7.0 | 5 / 16 | |
| 8.6.6 | 5 / 16 | |
| 8.6.5 | 5 / 16 | |
| 8.6.4 | 5 / 15 | |
| 8.6.3 | 5 / 15 | |
| 8.6.2 | 5 / 15 | |
| 8.6.1 | 5 / 14 | |
| 8.6.0 | 5 / 14 | |
| 8.5.0 | 4 / 14 | |
| 8.4.5 | 4 / 14 | |
| 8.4.4 | 4 / 14 | |
| 8.4.3 | 3 / 14 | |
| 8.4.2 | 3 / 14 | |
| 8.4.1 | 3 / 14 | |
| 8.4.0 | 3 / 13 | |
| 8.3.0 | 3 / 13 | |
| 8.2.1 | 3 / 13 | |
| 8.2.0 | 3 / 13 | |
| 8.1.0 | 3 / 13 | |
| 8.0.0 | 3 / 13 |
v8.10.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.
v8.10.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.
v8.9.6
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.9.5
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.9.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.9.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.
v8.9.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.
v8.9.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.
v8.9.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.
v8.8.5
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.8.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.8.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.
v8.8.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.
v8.8.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.
v8.8.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.
v8.7.7
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.7.6
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.7.5
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.7.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.7.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.
v8.7.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.
v8.7.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.
v8.7.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.
v8.6.6
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.6.5
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.6.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.6.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.
v8.6.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.
v8.6.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.
v8.6.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.
v8.5.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.
v8.4.5
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.4.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.4.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.
v8.4.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.
v8.4.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.
v8.4.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.
v8.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.
v8.2.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.
v8.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.
v8.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.
v8.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.