@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 — the axios compromise (March 2026) relied on exactly this gap.
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 36 of 145)
| Version | Deps | Published |
|---|---|---|
| 3.6.8 | 5 / 0 | |
| 3.6.7 | 5 / 0 | |
| 3.6.6 | 5 / 0 | |
| 3.6.5 | 5 / 0 | |
| 3.6.4 | 5 / 0 | |
| 3.6.3 | 5 / 0 | |
| 3.6.2 | 5 / 0 | |
| 3.6.1 | 5 / 0 | |
| 3.6.0 | 5 / 0 | |
| 3.5.3 | 5 / 1 | |
| 3.5.2 | 5 / 1 | |
| 3.5.1 | 5 / 1 | |
| 3.5.0 | 5 / 1 | |
| 3.4.10 | 5 / 1 | |
| 3.4.9 | 5 / 1 | |
| 3.4.8 | 5 / 1 | |
| 3.4.7 | 5 / 1 | |
| 3.4.6 | 5 / 1 | |
| 3.4.5 | 5 / 1 | |
| 3.4.4 | 5 / 1 | |
| 3.4.3 | 5 / 1 | |
| 3.4.2 | 5 / 1 | |
| 3.4.1 | 5 / 1 | |
| 3.4.0 | 5 / 1 | |
| 3.3.1 | 4 / 1 | |
| 3.3.0 | 4 / 1 | |
| 3.2.4 | 4 / 1 | |
| 3.2.3 | 4 / 1 | |
| 3.2.2 | 4 / 1 | |
| 3.2.1 | 4 / 1 | |
| 3.2.0 | 4 / 1 | |
| 3.1.2 | 4 / 1 | |
| 3.1.1 | 4 / 1 | |
| 3.1.0 | 4 / 1 | |
| 3.0.1 | 4 / 1 | |
| 3.0.0 | 4 / 1 |
v3.4.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.
v3.4.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.
v3.4.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.
v3.4.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.
v3.3.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.
v3.3.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.
v3.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.