@atlaskit/editor-plugin-block-menu
BlockMenu plugin for @atlaskit/editor-core
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Atlassian publishes the entire @atlaskit ecosystem without Sigstore provenance; this is consistent across all their packages and not a security concern for this publisher. | ai |
Versions (showing 51 of 258)
| Version | Deps | Published |
|---|---|---|
| 11.1.33 | 21 / 3 | |
| 11.1.32 | 21 / 3 | |
| 11.1.31 | 21 / 3 | |
| 11.1.30 | 21 / 3 | |
| 11.1.29 | 21 / 3 | |
| 11.1.28 | 21 / 3 | |
| 11.1.27 | 21 / 3 | |
| 11.1.26 | 21 / 3 | |
| 11.1.25 | 21 / 3 | |
| 11.1.24 | 21 / 3 | |
| 11.1.23 | 21 / 3 | |
| 11.1.22 | 21 / 3 | |
| 11.1.21 | 21 / 3 | |
| 11.1.20 | 21 / 3 | |
| 11.1.19 | 21 / 3 | |
| 11.1.18 | 21 / 3 | |
| 11.1.17 | 21 / 3 | |
| 11.1.16 | 20 / 3 | |
| 11.1.15 | 20 / 3 | |
| 11.1.14 | 20 / 3 | |
| 11.1.13 | 20 / 3 | |
| 11.1.12 | 20 / 3 | |
| 11.1.11 | 20 / 3 | |
| 11.1.10 | 20 / 3 | |
| 11.1.9 | 20 / 3 | |
| 11.1.8 | 20 / 3 | |
| 11.1.7 | 20 / 3 | |
| 11.1.6 | 20 / 3 | |
| 11.1.5 | 20 / 3 | |
| 11.1.4 | 20 / 3 | |
| 11.1.3 | 20 / 3 | |
| 11.1.2 | 20 / 3 | |
| 11.1.1 | 20 / 3 | |
| 11.1.0 | 20 / 3 | |
| 11.0.5 | 20 / 3 | |
| 11.0.4 | 20 / 3 | |
| 11.0.3 | 20 / 3 | |
| 11.0.2 | 20 / 3 | |
| 11.0.1 | 20 / 3 | |
| 11.0.0 | 20 / 3 | |
| 10.1.16 | 20 / 3 | |
| 10.1.15 | 20 / 3 | |
| 10.1.14 | 20 / 3 | |
| 10.1.13 | 20 / 3 | |
| 10.1.12 | 20 / 3 | |
| 10.1.11 | 20 / 3 | |
| 10.1.8 | 20 / 3 | |
| 10.1.7 | 20 / 3 | |
| 10.1.6 | 20 / 3 | |
| 10.1.5 | 20 / 3 | |
| 10.1.4 | 20 / 3 |
v11.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.