@telegraph/style-engine
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): Established monorepo package from knocklabs org; lack of provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@telegraph/tokens | AI (dependencies): Same-org sibling dependency within the knocklabs/telegraph monorepo; stable pattern across versions. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.3.9 | 2 / 14 | |
| 0.3.8 | 2 / 14 | |
| 0.3.7 | 2 / 14 | |
| 0.3.6 | 2 / 14 | |
| 0.3.5 | 2 / 14 | |
| 0.3.4 | 2 / 14 | |
| 0.3.2 | 2 / 14 | |
| 0.3.1 | 2 / 14 | |
| 0.2.2 | 2 / 14 | |
| 0.2.1 | 2 / 14 | |
| 0.2.0 | 2 / 14 | |
| 0.1.16 | 2 / 14 | |
| 0.1.15 | 2 / 14 | |
| 0.1.14 | 2 / 14 | |
| 0.1.13 | 2 / 14 | |
| 0.1.12 | 2 / 14 | |
| 0.1.11 | 5 / 14 | |
| 0.1.10 | 5 / 14 | |
| 0.1.9 | 5 / 14 | |
| 0.1.8 | 4 / 10 | |
| 0.1.7 | 4 / 10 | |
| 0.1.4 | 4 / 10 | |
| 0.1.3 | 4 / 10 | |
| 0.1.2 | 4 / 10 | |
| 0.1.1 | 4 / 10 | |
| 0.1.0 | 4 / 10 | |
| 0.0.5 | 4 / 10 | |
| 0.0.4 | 4 / 10 | |
| 0.0.3 | 4 / 10 | |
| 0.0.2 | 4 / 12 | |
| 0.0.1 | 3 / 12 |
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.