@atlaskit/editor-plugin-highlight
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 atlassianartifactteam publishes many packages without Sigstore provenance; this is consistent across their entire @atlaskit suite and not a risk indicator. | ai |
Versions (showing 51 of 176)
| Version | Deps | Published |
|---|---|---|
| 12.1.42 | 21 / 3 | |
| 12.1.41 | 21 / 3 | |
| 12.1.40 | 21 / 3 | |
| 12.1.39 | 21 / 3 | |
| 12.1.38 | 21 / 3 | |
| 12.1.37 | 21 / 3 | |
| 12.1.36 | 21 / 3 | |
| 12.1.35 | 21 / 3 | |
| 12.1.34 | 21 / 3 | |
| 12.1.33 | 21 / 3 | |
| 12.1.32 | 21 / 3 | |
| 12.1.31 | 21 / 3 | |
| 12.1.30 | 21 / 3 | |
| 12.1.29 | 21 / 3 | |
| 12.1.28 | 21 / 3 | |
| 12.1.27 | 21 / 3 | |
| 12.1.26 | 21 / 3 | |
| 12.1.25 | 21 / 3 | |
| 12.1.24 | 21 / 3 | |
| 12.1.23 | 21 / 3 | |
| 12.1.22 | 21 / 3 | |
| 12.1.21 | 21 / 3 | |
| 12.1.20 | 21 / 3 | |
| 12.1.19 | 21 / 3 | |
| 12.1.18 | 21 / 3 | |
| 12.1.17 | 21 / 3 | |
| 12.1.16 | 21 / 3 | |
| 12.1.15 | 21 / 3 | |
| 12.1.14 | 21 / 3 | |
| 12.1.13 | 21 / 3 | |
| 12.1.12 | 21 / 3 | |
| 12.1.11 | 21 / 3 | |
| 12.1.10 | 21 / 3 | |
| 12.1.9 | 21 / 3 | |
| 12.1.8 | 21 / 3 | |
| 12.1.7 | 21 / 3 | |
| 12.1.6 | 21 / 3 | |
| 12.1.5 | 21 / 3 | |
| 12.1.4 | 21 / 3 | |
| 12.1.3 | 21 / 3 | |
| 12.1.2 | 21 / 3 | |
| 12.1.1 | 21 / 3 | |
| 12.1.0 | 21 / 3 | |
| 12.0.2 | 21 / 3 | |
| 12.0.1 | 21 / 3 | |
| 12.0.0 | 21 / 3 | |
| 11.1.0 | 21 / 3 | |
| 11.0.17 | 21 / 3 | |
| 11.0.16 | 21 / 3 | |
| 11.0.15 | 21 / 3 | |
| 11.0.14 | 21 / 3 |
v12.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.