@atlaskit/editor-plugin-track-changes
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/icon-lab | AI (phantom-deps): Phantom dep within same @atlaskit org scope; common in monorepo packages where deps may be re-exported or used transitively. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tmp-editor-statsig | AI (phantom-deps): Phantom dep within same @atlaskit org scope; common in monorepo packages where deps may be re-exported or used transitively. | ai | |
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard npm alias for react-intl used consistently across the @atlaskit ecosystem; not a security risk. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-toolbar-model | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-history | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-toolbar | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/button | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-primary-toolbar | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org @atlaskit/* package declared but not directly imported; benign pattern in Atlaskit monorepo packages. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via atlassianartifactteam with strong track record; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-show-diff | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-toolbar | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): First-party Atlassian @atlaskit/* dependency; stable false positive for this package family. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 10.0.3 | 10 / 3 | |
| 10.0.2 | 10 / 3 | |
| 10.0.1 | 10 / 3 | |
| 10.0.0 | 10 / 3 | |
| 9.1.11 | 10 / 3 | |
| 9.1.10 | 10 / 3 | |
| 9.1.9 | 10 / 3 | |
| 9.1.8 | 10 / 3 | |
| 9.1.7 | 10 / 3 | |
| 9.1.6 | 10 / 3 | |
| 9.1.5 | 10 / 2 | |
| 9.1.4 | 10 / 2 | |
| 9.1.3 | 10 / 2 | |
| 9.1.2 | 10 / 2 | |
| 9.1.1 | 10 / 2 | |
| 9.1.0 | 10 / 2 | |
| 9.0.27 | 10 / 2 | |
| 9.0.26 | 10 / 2 | |
| 9.0.25 | 10 / 2 | |
| 9.0.24 | 10 / 2 | |
| 9.0.23 | 10 / 2 | |
| 9.0.22 | 10 / 2 | |
| 9.0.21 | 10 / 2 | |
| 9.0.20 | 10 / 2 | |
| 9.0.19 | 10 / 2 | |
| 9.0.18 | 10 / 2 | |
| 9.0.17 | 10 / 2 | |
| 9.0.16 | 10 / 2 | |
| 9.0.15 | 10 / 2 | |
| 9.0.14 | 10 / 2 | |
| 9.0.13 | 10 / 1 | |
| 9.0.12 | 10 / 1 | |
| 9.0.11 | 10 / 1 | |
| 9.0.10 | 10 / 1 | |
| 9.0.9 | 10 / 1 | |
| 9.0.8 | 10 / 1 | |
| 9.0.7 | 10 / 1 | |
| 9.0.6 | 10 / 1 | |
| 9.0.5 | 10 / 1 | |
| 9.0.4 | 10 / 1 | |
| 9.0.3 | 10 / 1 | |
| 9.0.2 | 10 / 1 | |
| 9.0.1 | 10 / 1 | |
| 9.0.0 | 10 / 1 | |
| 7.0.37 | 11 / 0 | |
| 7.0.36 | 11 / 0 | |
| 7.0.34 | 11 / 0 | |
| 7.0.33 | 11 / 0 | |
| 7.0.32 | 11 / 0 | |
| 7.0.31 | 11 / 0 | |
| 7.0.29 | 11 / 0 |
v10.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.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.
v7.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.