@atlaskit/editor-plugin-block-controls
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@atlaskit/link | AI (phantom-deps): Same @atlaskit org scope; phantom dep in monorepo context is a build artifact, not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/tokens | AI (phantom-deps): Same @atlaskit org scope; phantom dep in monorepo context is a build artifact, not a security concern. | ai | |
| phantom-deps | phantom-dep:@atlaskit/adf-schema | AI (phantom-deps): Same @atlaskit org scope; phantom dep in monorepo context is a build artifact, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): Atlassian publishes from their monorepo CI pipeline without Sigstore provenance; consistent across all their packages and not a security concern. | ai |
Versions (showing 100 of 272)
| Version | Deps | Published |
|---|---|---|
| 11.2.3 | 37 / 1 | |
| 11.2.2 | 37 / 1 | |
| 11.2.1 | 37 / 1 | |
| 11.2.0 | 37 / 1 | |
| 11.1.1 | 37 / 1 | |
| 11.1.0 | 37 / 1 | |
| 11.0.2 | 37 / 1 | |
| 11.0.1 | 37 / 1 | |
| 11.0.0 | 37 / 1 | |
| 10.0.0 | 37 / 0 | |
| 9.1.19 | 37 / 0 | |
| 9.1.18 | 37 / 0 | |
| 9.1.17 | 37 / 0 | |
| 9.1.16 | 37 / 0 | |
| 9.1.15 | 37 / 0 | |
| 9.1.13 | 37 / 0 | |
| 9.1.12 | 37 / 0 | |
| 9.1.11 | 37 / 0 | |
| 9.1.10 | 37 / 0 | |
| 9.1.9 | 37 / 0 | |
| 9.1.8 | 37 / 0 | |
| 9.1.7 | 37 / 0 | |
| 9.1.6 | 37 / 0 | |
| 9.1.5 | 37 / 0 | |
| 9.1.4 | 37 / 0 | |
| 9.1.3 | 37 / 0 | |
| 9.1.2 | 37 / 0 | |
| 9.1.1 | 37 / 0 | |
| 9.1.0 | 37 / 0 | |
| 9.0.33 | 37 / 0 | |
| 9.0.32 | 37 / 0 | |
| 9.0.31 | 37 / 0 | |
| 9.0.30 | 37 / 0 | |
| 9.0.29 | 37 / 0 | |
| 9.0.28 | 37 / 0 | |
| 9.0.27 | 37 / 0 | |
| 9.0.26 | 37 / 0 | |
| 9.0.25 | 37 / 0 | |
| 9.0.24 | 37 / 0 | |
| 9.0.23 | 37 / 0 | |
| 9.0.22 | 37 / 0 | |
| 9.0.21 | 37 / 0 | |
| 9.0.20 | 37 / 0 | |
| 9.0.19 | 37 / 0 | |
| 9.0.18 | 37 / 0 | |
| 9.0.17 | 37 / 0 | |
| 9.0.16 | 37 / 0 | |
| 9.0.15 | 37 / 0 | |
| 9.0.14 | 37 / 0 | |
| 9.0.13 | 37 / 0 | |
| 9.0.12 | 37 / 0 | |
| 9.0.11 | 37 / 0 | |
| 9.0.10 | 37 / 0 | |
| 9.0.8 | 37 / 0 | |
| 9.0.7 | 37 / 0 | |
| 9.0.6 | 37 / 0 | |
| 9.0.5 | 37 / 0 | |
| 9.0.4 | 37 / 0 | |
| 9.0.3 | 37 / 0 | |
| 9.0.2 | 37 / 0 | |
| 9.0.1 | 37 / 0 | |
| 9.0.0 | 37 / 0 | |
| 8.12.0 | 37 / 0 | |
| 8.11.0 | 37 / 0 | |
| 8.10.3 | 37 / 0 | |
| 8.10.2 | 37 / 0 | |
| 8.10.1 | 38 / 0 | |
| 8.10.0 | 38 / 0 | |
| 8.9.2 | 38 / 0 | |
| 8.9.1 | 38 / 0 | |
| 8.9.0 | 38 / 0 | |
| 8.8.2 | 38 / 0 | |
| 8.8.1 | 38 / 0 | |
| 8.8.0 | 38 / 0 | |
| 8.7.2 | 37 / 0 | |
| 8.7.1 | 37 / 0 | |
| 8.7.0 | 37 / 0 | |
| 8.6.4 | 37 / 0 | |
| 8.6.3 | 37 / 0 | |
| 8.6.2 | 37 / 0 | |
| 8.6.1 | 37 / 0 | |
| 8.6.0 | 37 / 0 | |
| 8.5.1 | 37 / 0 | |
| 8.5.0 | 37 / 0 | |
| 8.4.4 | 35 / 0 | |
| 8.4.3 | 35 / 0 | |
| 8.4.2 | 35 / 0 | |
| 8.4.1 | 35 / 0 | |
| 8.4.0 | 35 / 0 | |
| 8.3.4 | 36 / 0 | |
| 8.3.3 | 36 / 0 | |
| 8.3.2 | 36 / 0 | |
| 8.3.1 | 36 / 0 | |
| 8.3.0 | 36 / 0 | |
| 8.2.1 | 36 / 0 | |
| 8.2.0 | 36 / 0 | |
| 8.1.8 | 36 / 0 | |
| 8.1.7 | 36 / 0 | |
| 8.1.6 | 36 / 0 | |
| 8.1.5 | 36 / 0 |
v8.3.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.
v8.3.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.
v8.3.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.
v8.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.
v8.2.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.
v8.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.
v8.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.
v8.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.
v8.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.