@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 51 of 209)
| Version | Deps | Published |
|---|---|---|
| 3.0.33 | 4 / 1 | |
| 3.0.32 | 4 / 1 | |
| 3.0.31 | 4 / 1 | |
| 3.0.30 | 4 / 1 | |
| 3.0.29 | 4 / 1 | |
| 3.0.28 | 4 / 1 | |
| 3.0.27 | 4 / 1 | |
| 3.0.26 | 4 / 1 | |
| 3.0.25 | 4 / 1 | |
| 3.0.24 | 4 / 1 | |
| 3.0.23 | 4 / 1 | |
| 3.0.22 | 4 / 1 | |
| 3.0.21 | 4 / 1 | |
| 3.0.20 | 4 / 1 | |
| 3.0.19 | 4 / 1 | |
| 3.0.18 | 4 / 1 | |
| 3.0.17 | 4 / 1 | |
| 3.0.16 | 4 / 1 | |
| 3.0.15 | 4 / 1 | |
| 3.0.14 | 4 / 1 | |
| 3.0.13 | 4 / 1 | |
| 3.0.12 | 4 / 1 | |
| 3.0.11 | 4 / 1 | |
| 3.0.10 | 4 / 1 | |
| 3.0.9 | 4 / 1 | |
| 3.0.8 | 4 / 1 | |
| 3.0.7 | 4 / 1 | |
| 3.0.6 | 4 / 1 | |
| 3.0.5 | 4 / 1 | |
| 3.0.4 | 4 / 1 | |
| 3.0.3 | 4 / 1 | |
| 3.0.2 | 4 / 1 | |
| 3.0.1 | 4 / 1 | |
| 3.0.0 | 4 / 1 | |
| 2.10.23 | 4 / 1 | |
| 2.10.22 | 4 / 1 | |
| 2.10.21 | 4 / 1 | |
| 2.10.20 | 4 / 1 | |
| 2.10.19 | 4 / 1 | |
| 2.10.18 | 4 / 1 | |
| 2.10.15 | 4 / 1 | |
| 2.10.14 | 4 / 1 | |
| 2.10.13 | 4 / 1 | |
| 2.10.12 | 4 / 1 | |
| 2.10.11 | 4 / 1 | |
| 2.10.10 | 4 / 1 | |
| 2.10.9 | 4 / 1 | |
| 2.10.8 | 4 / 1 | |
| 2.10.7 | 4 / 1 | |
| 2.10.6 | 4 / 1 | |
| 2.10.5 | 4 / 1 |
v3.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.