@atlaskit/editor-palette
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 their atlaskit packages without Sigstore provenance; this is consistent across their entire package ecosystem and not a risk indicator. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 3.1.8 | 4 / 5 | |
| 3.1.7 | 4 / 5 | |
| 3.1.6 | 4 / 5 | |
| 3.1.5 | 4 / 5 | |
| 3.1.4 | 3 / 5 | |
| 3.1.3 | 3 / 5 | |
| 3.1.2 | 3 / 5 | |
| 3.1.1 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.0 | 2 / 4 | |
| 2.2.0 | 2 / 2 | |
| 2.1.26 | 2 / 2 | |
| 2.1.25 | 2 / 2 | |
| 2.1.24 | 2 / 2 | |
| 2.1.23 | 2 / 2 | |
| 2.1.22 | 2 / 2 | |
| 2.1.21 | 3 / 2 | |
| 2.1.20 | 3 / 2 | |
| 2.1.19 | 3 / 2 | |
| 2.1.18 | 3 / 2 | |
| 2.1.17 | 3 / 2 | |
| 2.1.16 | 3 / 2 | |
| 2.1.15 | 3 / 2 | |
| 2.1.14 | 3 / 2 | |
| 2.1.13 | 3 / 2 | |
| 2.1.12 | 3 / 2 | |
| 2.1.11 | 3 / 2 | |
| 2.1.10 | 3 / 3 | |
| 2.1.9 | 3 / 3 | |
| 2.1.8 | 3 / 3 | |
| 2.1.7 | 3 / 3 | |
| 2.1.6 | 3 / 3 | |
| 2.1.5 | 3 / 3 | |
| 2.1.4 | 3 / 3 | |
| 2.1.3 | 3 / 3 | |
| 2.1.2 | 3 / 3 | |
| 2.1.1 | 3 / 3 | |
| 2.1.0 | 3 / 3 | |
| 2.0.0 | 2 / 3 |
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.