@atlaskit/editor-plugin-mentions
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/css | AI (phantom-deps): Same-org scoped dependency in monorepo context; common pattern for explicit version management in Atlassian frontend infrastructure. | ai | |
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Same-org scoped dependency in monorepo context; common pattern for explicit version management in Atlassian frontend infrastructure. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same-org scoped dependency in monorepo context; common pattern for explicit version management in Atlassian frontend infrastructure. | ai |
Versions (showing 51 of 135)
| Version | Deps | Published |
|---|---|---|
| 13.3.0 | 29 / 5 | |
| 13.2.0 | 28 / 5 | |
| 13.1.1 | 28 / 5 | |
| 13.1.0 | 28 / 5 | |
| 13.0.0 | 28 / 5 | |
| 12.3.2 | 28 / 5 | |
| 12.3.1 | 28 / 5 | |
| 12.3.0 | 28 / 5 | |
| 12.2.11 | 28 / 5 | |
| 12.2.10 | 27 / 5 | |
| 12.2.9 | 27 / 5 | |
| 12.2.8 | 27 / 5 | |
| 12.2.7 | 27 / 5 | |
| 12.2.6 | 27 / 5 | |
| 12.2.5 | 27 / 3 | |
| 12.2.4 | 27 / 3 | |
| 12.2.3 | 27 / 3 | |
| 12.2.2 | 27 / 3 | |
| 12.2.1 | 27 / 3 | |
| 12.2.0 | 26 / 3 | |
| 12.1.17 | 26 / 3 | |
| 12.1.16 | 26 / 3 | |
| 12.1.15 | 26 / 3 | |
| 12.1.14 | 26 / 3 | |
| 12.1.13 | 26 / 3 | |
| 12.1.12 | 26 / 3 | |
| 12.1.11 | 26 / 3 | |
| 12.1.10 | 25 / 3 | |
| 12.1.9 | 25 / 3 | |
| 12.1.8 | 25 / 3 | |
| 12.1.7 | 25 / 3 | |
| 12.1.6 | 25 / 3 | |
| 12.1.5 | 25 / 3 | |
| 12.1.4 | 25 / 3 | |
| 12.1.3 | 25 / 3 | |
| 12.1.2 | 25 / 3 | |
| 12.1.1 | 25 / 3 | |
| 12.1.0 | 25 / 3 | |
| 12.0.2 | 25 / 3 | |
| 12.0.1 | 25 / 3 | |
| 12.0.0 | 25 / 3 | |
| 11.0.0 | 25 / 2 | |
| 10.0.34 | 25 / 2 | |
| 10.0.33 | 25 / 2 | |
| 10.0.32 | 25 / 2 | |
| 10.0.31 | 25 / 2 | |
| 10.0.30 | 25 / 2 | |
| 10.0.29 | 25 / 2 | |
| 10.0.28 | 25 / 2 | |
| 10.0.27 | 25 / 2 | |
| 10.0.26 | 25 / 2 |
v13.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.