@telegraph/layout
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): Stable monorepo package; missing description is a consistent pattern across the @telegraph/* scope, not a malware signal. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is consistent across all versions of this package; not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:@telegraph/compose-refs | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic likely fires due to re-export or indirect usage pattern in the monorepo. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.5.3 | 4 / 12 | |
| 0.5.2 | 4 / 12 | |
| 0.5.1 | 4 / 12 | |
| 0.5.0 | 4 / 12 | |
| 0.4.0 | 4 / 12 | |
| 0.3.3 | 4 / 12 | |
| 0.3.2 | 4 / 12 | |
| 0.3.1 | 4 / 12 | |
| 0.3.0 | 4 / 12 | |
| 0.2.3 | 4 / 12 | |
| 0.2.2 | 4 / 12 | |
| 0.2.1 | 4 / 12 | |
| 0.2.0 | 4 / 12 | |
| 0.1.21 | 4 / 12 | |
| 0.1.20 | 4 / 12 | |
| 0.1.19 | 4 / 12 | |
| 0.1.18 | 4 / 13 | |
| 0.1.17 | 4 / 13 | |
| 0.1.16 | 4 / 13 | |
| 0.1.15 | 4 / 13 | |
| 0.1.14 | 4 / 13 | |
| 0.1.13 | 4 / 13 | |
| 0.1.12 | 4 / 13 | |
| 0.1.11 | 4 / 13 | |
| 0.1.8 | 4 / 13 | |
| 0.1.6 | 4 / 13 | |
| 0.1.5 | 4 / 13 | |
| 0.1.4 | 4 / 13 | |
| 0.1.3 | 4 / 13 | |
| 0.1.2 | 4 / 13 | |
| 0.1.1 | 4 / 13 | |
| 0.1.0 | 4 / 13 | |
| 0.0.30 | 5 / 12 | |
| 0.0.29 | 5 / 12 | |
| 0.0.28 | 5 / 12 | |
| 0.0.27 | 5 / 12 | |
| 0.0.26 | 5 / 12 | |
| 0.0.25 | 5 / 12 | |
| 0.0.24 | 5 / 12 | |
| 0.0.23 | 5 / 12 | |
| 0.0.22 | 5 / 12 | |
| 0.0.21 | 5 / 12 | |
| 0.0.20 | 5 / 14 | |
| 0.0.19 | 5 / 14 | |
| 0.0.18 | 4 / 15 | |
| 0.0.17 | 4 / 14 | |
| 0.0.16 | 4 / 14 | |
| 0.0.15 | 4 / 14 | |
| 0.0.14 | 4 / 14 | |
| 0.0.13 | 4 / 14 | |
| 0.0.12 | 4 / 14 |
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
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.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.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.