@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 72 of 272)
| Version | Deps | Published |
|---|---|---|
| 8.1.4 | 36 / 0 | |
| 8.1.3 | 36 / 0 | |
| 8.1.2 | 36 / 0 | |
| 8.1.1 | 36 / 0 | |
| 8.1.0 | 36 / 0 | |
| 8.0.15 | 36 / 0 | |
| 8.0.14 | 36 / 0 | |
| 8.0.13 | 36 / 0 | |
| 8.0.12 | 36 / 0 | |
| 8.0.11 | 36 / 0 | |
| 8.0.10 | 36 / 0 | |
| 8.0.9 | 36 / 0 | |
| 8.0.8 | 36 / 0 | |
| 8.0.7 | 36 / 0 | |
| 8.0.6 | 36 / 0 | |
| 8.0.5 | 36 / 0 | |
| 8.0.4 | 36 / 0 | |
| 8.0.3 | 36 / 0 | |
| 8.0.2 | 36 / 0 | |
| 8.0.1 | 36 / 0 | |
| 8.0.0 | 36 / 0 | |
| 7.19.0 | 36 / 0 | |
| 7.18.3 | 36 / 0 | |
| 7.18.2 | 36 / 0 | |
| 7.18.1 | 36 / 0 | |
| 7.18.0 | 36 / 0 | |
| 7.17.2 | 36 / 0 | |
| 7.17.1 | 36 / 0 | |
| 7.17.0 | 36 / 0 | |
| 7.16.0 | 36 / 0 | |
| 7.15.3 | 36 / 0 | |
| 7.15.2 | 36 / 0 | |
| 7.15.1 | 36 / 0 | |
| 7.15.0 | 36 / 0 | |
| 7.14.1 | 36 / 0 | |
| 7.14.0 | 36 / 0 | |
| 7.13.3 | 36 / 0 | |
| 7.13.2 | 36 / 0 | |
| 7.13.1 | 36 / 0 | |
| 7.13.0 | 36 / 0 | |
| 7.12.1 | 36 / 0 | |
| 7.12.0 | 36 / 0 | |
| 7.11.4 | 36 / 0 | |
| 7.11.3 | 36 / 0 | |
| 7.11.2 | 36 / 0 | |
| 7.11.1 | 36 / 0 | |
| 7.11.0 | 36 / 0 | |
| 7.10.2 | 36 / 0 | |
| 7.10.1 | 36 / 0 | |
| 7.10.0 | 36 / 0 | |
| 7.9.0 | 36 / 0 | |
| 7.8.0 | 36 / 0 | |
| 7.7.9 | 36 / 0 | |
| 7.7.8 | 36 / 0 | |
| 7.7.7 | 36 / 0 | |
| 7.7.6 | 36 / 0 | |
| 7.7.5 | 36 / 0 | |
| 7.7.4 | 36 / 0 | |
| 7.7.3 | 36 / 0 | |
| 7.7.2 | 35 / 0 | |
| 7.7.1 | 35 / 0 | |
| 7.7.0 | 35 / 0 | |
| 7.6.0 | 35 / 0 | |
| 7.5.10 | 35 / 0 | |
| 7.5.9 | 35 / 0 | |
| 7.5.8 | 35 / 0 | |
| 7.5.7 | 35 / 0 | |
| 7.5.6 | 35 / 0 | |
| 7.5.5 | 35 / 0 | |
| 7.5.4 | 35 / 0 | |
| 7.5.3 | 35 / 0 | |
| 7.5.2 | 35 / 0 |
v8.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.
v8.1.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.1.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.1.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.1.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.0.15
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.0.14
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.0.13
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.0.12
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.0.11
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.0.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.
v8.0.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.0.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.0.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.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.
v8.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.
v8.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.
v8.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.
v7.19.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.
v7.18.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.18.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.
v7.18.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.
v7.17.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.
v7.17.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.
v7.16.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.
v7.15.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.15.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.
v7.15.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.
v7.14.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.
v7.13.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.
v7.13.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.
v7.13.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.
v7.12.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.
v7.11.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.
v7.11.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.11.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.
v7.11.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.
v7.11.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.
v7.10.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.
v7.10.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.
v7.9.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.
v7.8.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.
v7.7.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.7.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.7.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.7.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.7.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.
v7.7.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.
v7.7.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.
v7.7.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.
v7.6.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.
v7.5.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.
v7.5.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.
v7.5.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.5.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.5.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.
v7.5.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.