@atlaskit/editor-plugin-floating-toolbar
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 npm alias for react-intl@^5.x used throughout the Atlaskit ecosystem; resolves to the canonical react-intl package, not a suspicious dependency. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes the entire @atlaskit suite without Sigstore provenance; this is consistent across all their packages and not a risk signal. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit dependency declared but not directly imported; expected pattern for Atlaskit packages using shared design tokens. | ai | |
| phantom-deps | phantom-dep:@atlaskit/adf-utils | AI (phantom-deps): Same-org @atlaskit dependency; phantom usage is benign in the Atlaskit monorepo ecosystem. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org @atlaskit dependency; phantom usage is benign in the Atlaskit monorepo ecosystem. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 13.0.1 | 31 / 8 | |
| 13.0.0 | 31 / 8 | |
| 12.2.5 | 31 / 8 | |
| 12.2.4 | 31 / 8 | |
| 12.2.3 | 31 / 8 | |
| 12.2.2 | 31 / 8 | |
| 12.2.1 | 31 / 8 | |
| 12.2.0 | 31 / 8 | |
| 12.1.3 | 31 / 6 | |
| 12.1.2 | 31 / 6 | |
| 12.1.1 | 31 / 6 | |
| 12.1.0 | 31 / 6 | |
| 12.0.20 | 31 / 6 | |
| 12.0.19 | 31 / 6 | |
| 12.0.18 | 31 / 6 | |
| 12.0.17 | 31 / 6 | |
| 12.0.16 | 31 / 6 | |
| 12.0.15 | 31 / 6 | |
| 12.0.14 | 31 / 6 | |
| 12.0.13 | 31 / 6 | |
| 12.0.12 | 31 / 6 | |
| 12.0.11 | 31 / 6 | |
| 12.0.10 | 31 / 6 | |
| 12.0.9 | 31 / 6 | |
| 12.0.8 | 31 / 6 | |
| 12.0.7 | 31 / 6 | |
| 12.0.6 | 31 / 6 | |
| 12.0.5 | 31 / 6 | |
| 12.0.4 | 31 / 6 | |
| 12.0.3 | 31 / 6 | |
| 12.0.2 | 31 / 6 | |
| 12.0.1 | 31 / 6 | |
| 12.0.0 | 31 / 6 | |
| 10.0.24 | 32 / 5 | |
| 10.0.21 | 32 / 5 | |
| 10.0.19 | 32 / 5 | |
| 10.0.17 | 32 / 5 | |
| 10.0.16 | 32 / 5 | |
| 10.0.15 | 32 / 5 | |
| 10.0.13 | 33 / 5 | |
| 8.2.10 | 34 / 5 |
v13.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.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.
v12.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.
v10.0.24
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.21
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.19
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.17
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.16
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.15
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.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.2.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.