@atlaskit/editor-plugin-code-bidi-warning
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:@atlaskit/code | AI (dependencies): Same-org @atlaskit scoped dependency from Atlassian; not a meaningful risk for this publisher. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-prosemirror | AI (dependencies): Same-org @atlaskit scoped dependency from Atlassian; not a meaningful risk for this publisher. | ai | |
| dependencies | unvetted-dep:@atlaskit/tmp-editor-statsig | AI (dependencies): Same-org @atlaskit scoped dependency from Atlassian; not a meaningful risk for this publisher. | ai | |
| dependencies | unvetted-dep:@atlaskit/platform-feature-flags | AI (dependencies): Same-org @atlaskit scoped dependency from Atlassian; not a meaningful risk for this publisher. | ai | |
| dependencies | unvetted-dep:@atlaskit/editor-plugin-limited-mode | AI (dependencies): Same-org @atlaskit scoped dependency from Atlassian; not a meaningful risk for this publisher. | ai | |
| phantom-deps | phantom-dep:@atlaskit/platform-feature-flags | AI (phantom-deps): Same-org phantom dep; minor code quality issue, not a security concern for this Atlassian package. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 11.0.1 | 7 / 4 | |
| 11.0.0 | 7 / 4 | |
| 10.1.7 | 7 / 4 | |
| 10.1.6 | 7 / 4 | |
| 10.1.5 | 7 / 4 | |
| 10.1.4 | 7 / 4 | |
| 10.1.3 | 7 / 4 | |
| 10.1.2 | 7 / 2 | |
| 10.1.1 | 7 / 2 | |
| 10.1.0 | 7 / 2 | |
| 10.0.18 | 7 / 2 | |
| 10.0.17 | 7 / 2 | |
| 10.0.16 | 7 / 2 | |
| 10.0.15 | 7 / 2 | |
| 10.0.14 | 7 / 2 | |
| 10.0.13 | 7 / 2 | |
| 10.0.12 | 7 / 2 | |
| 10.0.11 | 7 / 2 | |
| 10.0.10 | 7 / 2 | |
| 10.0.9 | 7 / 2 | |
| 10.0.8 | 7 / 2 | |
| 10.0.7 | 7 / 2 | |
| 10.0.6 | 7 / 2 | |
| 10.0.5 | 7 / 2 | |
| 10.0.4 | 7 / 2 | |
| 10.0.3 | 7 / 2 | |
| 10.0.2 | 7 / 2 | |
| 10.0.1 | 7 / 2 | |
| 10.0.0 | 7 / 2 | |
| 9.0.0 | 7 / 2 | |
| 8.0.31 | 7 / 2 | |
| 8.0.30 | 7 / 2 | |
| 8.0.29 | 7 / 2 | |
| 8.0.28 | 7 / 2 | |
| 8.0.27 | 7 / 2 | |
| 8.0.26 | 7 / 2 | |
| 8.0.25 | 7 / 2 | |
| 8.0.24 | 7 / 2 | |
| 8.0.23 | 7 / 2 | |
| 8.0.22 | 7 / 2 | |
| 8.0.21 | 7 / 2 | |
| 8.0.20 | 7 / 2 | |
| 8.0.19 | 7 / 2 | |
| 8.0.18 | 7 / 2 | |
| 8.0.17 | 7 / 2 | |
| 8.0.16 | 7 / 2 | |
| 8.0.15 | 7 / 2 | |
| 8.0.14 | 7 / 2 | |
| 8.0.13 | 7 / 2 | |
| 8.0.12 | 7 / 2 | |
| 8.0.11 | 7 / 2 |
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.