tex-to-typst
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is GitHub Actions with SLSA attestation; CI/CD publishing is the expected pattern for this org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-attested publish from same org repo; no compromise indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): unified is a widely-used, well-maintained remark/rehype ecosystem package; low risk. | ai | |
| phantom-deps | phantom-dep:@unified-latex/unified-latex | AI (phantom-deps): Used in config/peer context, not directly imported; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.20 | 4 / 13 | |
| 0.0.19 | 3 / 7 | |
| 0.0.18 | 3 / 7 | |
| 0.0.17 | 3 / 7 |
v0.0.20
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.