@atlaskit/editor-plugin-status
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/tokens | AI (phantom-deps): @atlaskit/tokens is a first-party Atlassian package in the same org scope; phantom dep finding is a minor code quality issue, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes many packages without Sigstore provenance; publisher track record (177 approved) provides sufficient trust signal. | ai |
Versions (showing 21 of 131)
| Version | Deps | Published |
|---|---|---|
| 8.1.5 | 14 / 2 | |
| 8.1.4 | 14 / 2 | |
| 8.1.3 | 14 / 2 | |
| 8.1.2 | 14 / 2 | |
| 8.1.1 | 14 / 2 | |
| 8.1.0 | 14 / 2 | |
| 8.0.0 | 14 / 2 | |
| 7.1.17 | 14 / 2 | |
| 7.1.16 | 14 / 2 | |
| 7.1.15 | 14 / 2 | |
| 7.1.14 | 14 / 2 | |
| 7.1.13 | 14 / 2 | |
| 7.1.12 | 14 / 2 | |
| 7.1.11 | 14 / 2 | |
| 7.1.10 | 14 / 2 | |
| 7.1.9 | 14 / 4 | |
| 7.1.8 | 14 / 4 | |
| 7.1.7 | 14 / 4 | |
| 7.1.6 | 14 / 4 | |
| 7.1.5 | 14 / 4 | |
| 7.1.4 | 14 / 4 |
v8.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.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.
v7.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.
v7.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.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.
v7.1.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.