@atlaskit/editor-plugin-paste-options-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 Atlassian ecosystem alias for react-intl (npm:react-intl@^5.18.1). This aliasing pattern is used consistently across Atlassian packages and poses no security risk. | ai | |
| phantom-deps | phantom-dep:@atlaskit/css | AI (phantom-deps): Same-org @atlaskit/* phantom dep; declared for type resolution or build tooling, not a security concern for this Atlassian package. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org @atlaskit/* phantom dep; declared for type resolution or build tooling, not a security concern for this Atlassian package. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Referenced in config files but not directly imported; standard pattern for emotion-based styling in Atlassian 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 indicator here. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 12.0.1 | 18 / 5 | |
| 12.0.0 | 18 / 5 | |
| 11.4.1 | 18 / 5 | |
| 11.4.0 | 18 / 5 | |
| 11.3.3 | 18 / 5 | |
| 11.3.2 | 18 / 5 | |
| 11.3.1 | 18 / 5 | |
| 11.3.0 | 18 / 5 | |
| 11.2.3 | 18 / 3 | |
| 11.2.2 | 18 / 3 | |
| 11.2.1 | 18 / 3 | |
| 11.2.0 | 18 / 3 | |
| 11.1.0 | 18 / 3 | |
| 11.0.21 | 18 / 3 | |
| 11.0.20 | 18 / 3 | |
| 11.0.19 | 18 / 3 | |
| 11.0.18 | 18 / 3 | |
| 11.0.17 | 18 / 3 | |
| 11.0.16 | 18 / 3 | |
| 11.0.15 | 18 / 3 | |
| 11.0.14 | 18 / 3 | |
| 11.0.13 | 18 / 3 | |
| 11.0.12 | 18 / 3 | |
| 11.0.11 | 18 / 3 | |
| 11.0.10 | 18 / 3 | |
| 11.0.9 | 18 / 3 | |
| 11.0.7 | 18 / 3 | |
| 11.0.6 | 18 / 3 | |
| 11.0.5 | 18 / 3 | |
| 11.0.4 | 18 / 3 | |
| 11.0.3 | 18 / 3 | |
| 11.0.2 | 18 / 3 | |
| 11.0.1 | 18 / 3 | |
| 11.0.0 | 18 / 3 | |
| 9.2.10 | 19 / 2 | |
| 9.2.9 | 19 / 2 | |
| 9.2.8 | 19 / 2 | |
| 9.2.6 | 19 / 2 | |
| 9.2.3 | 19 / 2 | |
| 9.2.1 | 19 / 2 | |
| 9.1.6 | 17 / 2 | |
| 7.0.3 | 10 / 4 | |
| 7.0.2 | 10 / 4 |
v12.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.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.
v11.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.
v9.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.
v9.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.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.
v9.2.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.
v9.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.
v9.1.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.
v7.0.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.
v7.0.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.