@atlaskit/editor-shared-styles
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's atlaskit packages are published without Sigstore provenance; this is consistent across all versions and not a security concern for this well-established publisher. | ai |
Versions (showing 51 of 174)
| Version | Deps | Published |
|---|---|---|
| 4.0.33 | 5 / 0 | |
| 4.0.32 | 5 / 0 | |
| 4.0.31 | 5 / 0 | |
| 4.0.30 | 5 / 0 | |
| 4.0.29 | 5 / 0 | |
| 4.0.28 | 5 / 0 | |
| 4.0.27 | 5 / 0 | |
| 4.0.26 | 5 / 0 | |
| 4.0.25 | 5 / 0 | |
| 4.0.24 | 5 / 0 | |
| 4.0.23 | 5 / 0 | |
| 4.0.22 | 5 / 0 | |
| 4.0.21 | 5 / 0 | |
| 4.0.20 | 5 / 0 | |
| 4.0.19 | 5 / 0 | |
| 4.0.18 | 5 / 0 | |
| 4.0.17 | 5 / 0 | |
| 4.0.16 | 5 / 0 | |
| 4.0.15 | 5 / 0 | |
| 4.0.14 | 5 / 0 | |
| 4.0.13 | 5 / 0 | |
| 4.0.12 | 5 / 0 | |
| 4.0.11 | 5 / 0 | |
| 4.0.10 | 5 / 0 | |
| 4.0.9 | 5 / 0 | |
| 4.0.8 | 5 / 0 | |
| 4.0.7 | 5 / 0 | |
| 4.0.6 | 5 / 0 | |
| 4.0.5 | 5 / 0 | |
| 4.0.4 | 5 / 0 | |
| 4.0.3 | 5 / 0 | |
| 4.0.2 | 5 / 0 | |
| 4.0.1 | 5 / 0 | |
| 4.0.0 | 5 / 0 | |
| 3.11.24 | 5 / 0 | |
| 3.11.23 | 5 / 0 | |
| 3.11.22 | 5 / 0 | |
| 3.11.21 | 5 / 0 | |
| 3.11.20 | 5 / 0 | |
| 3.11.19 | 5 / 0 | |
| 3.11.16 | 5 / 0 | |
| 3.11.15 | 5 / 0 | |
| 3.11.14 | 5 / 0 | |
| 3.11.13 | 5 / 0 | |
| 3.11.12 | 5 / 0 | |
| 3.11.11 | 5 / 0 | |
| 3.11.10 | 5 / 0 | |
| 3.11.9 | 5 / 0 | |
| 3.11.8 | 5 / 0 | |
| 3.11.7 | 5 / 0 | |
| 3.11.6 | 5 / 0 |
v4.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.