@atlaskit/editor-plugin-text-formatting
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:react-intl-next | AI (dependencies): react-intl-next is a standard Atlassian alias for react-intl (npm:react-intl@^5.18.1), used consistently across the entire Atlaskit monorepo. Not a suspicious dependency. | ai | |
| dependencies | unvetted-dep:@atlaskit/tokens | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/adf-schema | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-tables | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-toolbar | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-base | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-shared-styles | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/icon | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-toolbar | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-analytics | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/prosemirror-input-rules | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-primary-toolbar | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-selection-toolbar | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes via their artifact team pipeline without Sigstore provenance; consistent across all their packages and not a security concern. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-toolbar-model | AI (dependencies): Official Atlaskit package from Atlassian; unvetted status is a registry gap, not a security concern. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 18 / 3 | |
| 11.0.0 | 18 / 3 | |
| 10.2.4 | 18 / 3 | |
| 10.2.3 | 18 / 3 | |
| 10.2.2 | 18 / 3 | |
| 10.2.1 | 18 / 3 | |
| 10.2.0 | 18 / 3 | |
| 10.1.6 | 18 / 3 | |
| 10.1.5 | 18 / 3 | |
| 10.1.4 | 18 / 2 | |
| 10.1.3 | 18 / 2 | |
| 10.1.2 | 18 / 2 | |
| 10.1.1 | 18 / 2 | |
| 10.1.0 | 18 / 2 | |
| 10.0.18 | 18 / 2 | |
| 10.0.17 | 18 / 2 | |
| 10.0.16 | 18 / 2 | |
| 10.0.15 | 18 / 2 | |
| 10.0.14 | 18 / 2 | |
| 10.0.13 | 18 / 2 | |
| 10.0.12 | 18 / 2 | |
| 10.0.11 | 18 / 2 | |
| 10.0.10 | 18 / 2 | |
| 10.0.9 | 18 / 2 | |
| 10.0.8 | 18 / 2 | |
| 10.0.7 | 18 / 2 | |
| 10.0.6 | 18 / 2 | |
| 10.0.5 | 18 / 2 | |
| 10.0.4 | 18 / 2 | |
| 10.0.3 | 18 / 2 | |
| 10.0.2 | 18 / 2 | |
| 10.0.1 | 18 / 2 | |
| 10.0.0 | 18 / 2 | |
| 8.2.11 | 19 / 1 | |
| 8.2.7 | 19 / 1 | |
| 8.2.6 | 19 / 1 | |
| 8.2.4 | 19 / 1 | |
| 8.2.2 | 19 / 1 | |
| 8.2.1 | 19 / 1 | |
| 8.2.0 | 19 / 1 | |
| 8.1.13 | 19 / 1 | |
| 8.1.10 | 19 / 1 | |
| 8.1.7 | 19 / 1 | |
| 6.1.5 | 19 / 4 |
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.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.
v8.2.11
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.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.2.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.2.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.2.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.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.13
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.10
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.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.
v6.1.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.