@telegraph/icon
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Intentional for this monorepo package; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 72 versions; org-wide pattern, not a new anomaly. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 4 / 11 | |
| 0.5.3 | 4 / 11 | |
| 0.5.2 | 4 / 11 | |
| 0.5.1 | 4 / 11 | |
| 0.5.0 | 4 / 11 | |
| 0.4.1 | 4 / 11 | |
| 0.4.0 | 4 / 11 | |
| 0.3.5 | 4 / 11 | |
| 0.3.4 | 4 / 11 | |
| 0.3.3 | 4 / 11 | |
| 0.3.2 | 4 / 11 | |
| 0.3.1 | 4 / 11 | |
| 0.3.0 | 4 / 11 | |
| 0.2.7 | 4 / 11 | |
| 0.2.6 | 4 / 11 | |
| 0.2.5 | 4 / 11 | |
| 0.2.4 | 4 / 11 | |
| 0.2.3 | 4 / 11 | |
| 0.2.2 | 4 / 11 | |
| 0.2.1 | 4 / 11 | |
| 0.2.0 | 4 / 11 | |
| 0.1.1 | 4 / 11 | |
| 0.1.0 | 4 / 11 | |
| 0.0.50 | 4 / 11 | |
| 0.0.49 | 4 / 11 | |
| 0.0.48 | 4 / 11 | |
| 0.0.47 | 4 / 11 | |
| 0.0.46 | 4 / 11 | |
| 0.0.45 | 4 / 11 | |
| 0.0.42 | 4 / 11 | |
| 0.0.41 | 4 / 11 | |
| 0.0.40 | 4 / 11 | |
| 0.0.39 | 4 / 11 | |
| 0.0.38 | 4 / 11 | |
| 0.0.37 | 4 / 11 | |
| 0.0.36 | 4 / 12 | |
| 0.0.35 | 4 / 12 | |
| 0.0.34 | 4 / 12 | |
| 0.0.33 | 4 / 12 | |
| 0.0.32 | 4 / 12 | |
| 0.0.31 | 4 / 12 | |
| 0.0.30 | 4 / 12 | |
| 0.0.29 | 4 / 12 | |
| 0.0.28 | 4 / 12 | |
| 0.0.27 | 4 / 12 | |
| 0.0.26 | 4 / 12 | |
| 0.0.25 | 4 / 12 | |
| 0.0.24 | 4 / 12 | |
| 0.0.23 | 4 / 12 | |
| 0.0.22 | 4 / 12 | |
| 0.0.21 | 3 / 14 |
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.