@atlaskit/editor-tables
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 publishing pipeline does not use Sigstore provenance; this is consistent across all @atlaskit packages and is not a security concern. | ai |
Versions (showing 100 of 209)
| Version | Deps | Published |
|---|---|---|
| 2.9.46 | 4 / 1 | |
| 2.9.45 | 4 / 1 | |
| 2.9.44 | 4 / 1 | |
| 2.9.43 | 4 / 1 | |
| 2.9.42 | 4 / 1 | |
| 2.9.41 | 4 / 1 | |
| 2.9.40 | 4 / 1 | |
| 2.9.39 | 4 / 1 | |
| 2.9.38 | 4 / 1 | |
| 2.9.37 | 4 / 1 | |
| 2.9.36 | 4 / 1 | |
| 2.9.35 | 4 / 1 | |
| 2.9.34 | 4 / 1 | |
| 2.9.33 | 4 / 1 | |
| 2.9.32 | 4 / 1 | |
| 2.9.31 | 4 / 1 | |
| 2.9.30 | 4 / 1 | |
| 2.9.29 | 4 / 1 | |
| 2.9.28 | 4 / 1 | |
| 2.9.27 | 4 / 1 | |
| 2.9.26 | 4 / 1 | |
| 2.9.25 | 4 / 1 | |
| 2.9.24 | 4 / 1 | |
| 2.9.23 | 4 / 0 | |
| 2.9.22 | 4 / 0 | |
| 2.9.21 | 4 / 0 | |
| 2.9.20 | 4 / 0 | |
| 2.9.19 | 4 / 0 | |
| 2.9.18 | 4 / 0 | |
| 2.9.17 | 4 / 0 | |
| 2.9.16 | 4 / 0 | |
| 2.9.15 | 4 / 0 | |
| 2.9.14 | 4 / 0 | |
| 2.9.13 | 4 / 0 | |
| 2.9.12 | 4 / 0 | |
| 2.9.11 | 4 / 0 | |
| 2.9.10 | 4 / 0 | |
| 2.9.9 | 4 / 0 | |
| 2.9.8 | 4 / 0 | |
| 2.9.7 | 4 / 0 | |
| 2.9.6 | 4 / 0 | |
| 2.9.5 | 4 / 0 | |
| 2.9.4 | 4 / 0 | |
| 2.9.3 | 4 / 0 | |
| 2.9.2 | 4 / 0 | |
| 2.9.1 | 4 / 0 | |
| 2.9.0 | 3 / 0 | |
| 2.8.6 | 3 / 0 | |
| 2.8.5 | 3 / 0 | |
| 2.8.4 | 3 / 0 | |
| 2.8.3 | 3 / 0 | |
| 2.8.2 | 2 / 0 | |
| 2.8.1 | 2 / 0 | |
| 2.8.0 | 2 / 0 | |
| 2.7.5 | 2 / 1 | |
| 2.7.4 | 2 / 2 | |
| 2.7.3 | 2 / 2 | |
| 2.7.2 | 2 / 2 | |
| 2.7.1 | 2 / 2 | |
| 2.7.0 | 2 / 2 | |
| 2.6.3 | 2 / 2 | |
| 2.6.2 | 3 / 2 | |
| 2.6.1 | 3 / 2 | |
| 2.6.0 | 3 / 2 | |
| 2.5.8 | 3 / 2 | |
| 2.5.7 | 3 / 2 | |
| 2.5.6 | 3 / 2 | |
| 2.5.5 | 3 / 2 | |
| 2.5.4 | 3 / 2 | |
| 2.5.3 | 3 / 2 | |
| 2.5.2 | 3 / 2 | |
| 2.5.1 | 3 / 2 | |
| 2.5.0 | 3 / 2 | |
| 2.4.0 | 3 / 2 | |
| 2.3.18 | 3 / 2 | |
| 2.3.17 | 3 / 2 | |
| 2.3.16 | 3 / 2 | |
| 2.3.15 | 3 / 2 | |
| 2.3.14 | 3 / 2 | |
| 2.3.13 | 3 / 2 | |
| 2.3.12 | 3 / 2 | |
| 2.3.11 | 3 / 1 | |
| 2.3.10 | 3 / 1 | |
| 2.3.9 | 3 / 1 | |
| 2.3.8 | 2 / 2 | |
| 2.3.7 | 2 / 2 | |
| 2.3.6 | 7 / 2 | |
| 2.3.5 | 7 / 2 | |
| 2.3.4 | 7 / 2 | |
| 2.3.3 | 7 / 3 | |
| 2.3.2 | 7 / 3 | |
| 2.3.1 | 7 / 3 | |
| 2.3.0 | 7 / 3 | |
| 2.2.6 | 7 / 3 | |
| 2.2.5 | 7 / 3 | |
| 2.2.4 | 7 / 3 | |
| 2.2.3 | 7 / 3 | |
| 2.2.2 | 7 / 3 | |
| 2.2.1 | 7 / 3 | |
| 2.2.0 | 7 / 3 |
v2.6.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.
v2.6.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.
v2.6.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.
v2.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.
v2.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.
v2.5.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.
v2.5.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.
v2.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.
v2.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.
v2.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.
v2.5.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.
v2.5.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.
v2.5.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.
v2.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.
v2.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.3.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.
v2.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.
v2.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.
v2.2.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.
v2.2.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.
v2.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.
v2.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.
v2.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.
v2.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.
v2.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.