@financial-times/o-teaser
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo component. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo component. | ai | |
| phantom-deps | phantom-dep:dateformat | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo component. | ai | |
| phantom-deps | phantom-dep:html-react-parser | AI (phantom-deps): Config-referenced dependency; stable pattern for this monorepo component. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 10.0.4 | 4 / 5 | |
| 10.0.3 | 4 / 5 | |
| 10.0.1 | 4 / 5 | |
| 10.0.0 | 4 / 5 | |
| 9.1.3 | 4 / 5 | |
| 9.1.2 | 4 / 5 | |
| 9.1.1 | 4 / 5 |
v10.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.