@telegraph/modal
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by framer-motion→motion migration; motion bundles more code by design. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): motion and lucide-react are well-established packages replacing framer-motion; not suspicious. | ai | |
| phantom-deps | phantom-dep:@telegraph/icon | AI (phantom-deps): Same-org sibling dep; likely used transitively or via re-export pattern in this monorepo. | ai | |
| phantom-deps | phantom-dep:@telegraph/style-engine | AI (phantom-deps): Same-org sibling dep; same monorepo transitive usage pattern. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 0.2.2 | 12 / 11 | |
| 0.2.1 | 12 / 11 | |
| 0.2.0 | 12 / 11 | |
| 0.1.22 | 12 / 11 | |
| 0.1.21 | 11 / 11 | |
| 0.1.20 | 11 / 11 | |
| 0.1.19 | 11 / 11 | |
| 0.1.18 | 11 / 11 | |
| 0.1.17 | 11 / 11 | |
| 0.1.16 | 11 / 11 | |
| 0.1.15 | 11 / 11 | |
| 0.1.14 | 11 / 11 | |
| 0.1.13 | 11 / 11 | |
| 0.1.12 | 11 / 11 | |
| 0.1.11 | 11 / 11 | |
| 0.1.10 | 11 / 11 | |
| 0.1.9 | 11 / 11 | |
| 0.1.8 | 11 / 11 | |
| 0.1.7 | 11 / 11 | |
| 0.1.6 | 11 / 11 | |
| 0.1.5 | 11 / 11 | |
| 0.1.4 | 11 / 11 | |
| 0.1.3 | 11 / 11 | |
| 0.1.2 | 11 / 11 | |
| 0.1.1 | 11 / 11 | |
| 0.1.0 | 11 / 11 | |
| 0.0.86 | 11 / 11 | |
| 0.0.85 | 11 / 11 | |
| 0.0.84 | 10 / 11 | |
| 0.0.83 | 10 / 11 | |
| 0.0.82 | 10 / 11 | |
| 0.0.81 | 10 / 11 | |
| 0.0.80 | 10 / 11 | |
| 0.0.79 | 10 / 11 |
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.