@pretextbook/latex-pretext
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep for TypeScript-compiled packages; stable false positive. | ai | |
| phantom-deps | phantom-dep:@unified-latex/unified-latex-types | AI (phantom-deps): Referenced in config/type definitions rather than direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@unified-latex/unified-latex-util-parse | AI (phantom-deps): Referenced in config files rather than direct imports; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 4 / 2 | |
| 0.0.9 | 4 / 2 | |
| 0.0.7 | 4 / 0 | |
| 0.0.6 | 4 / 0 | |
| 0.0.3 | 4 / 0 | |
| 0.0.2 | 3 / 0 | |
| 0.0.1 | 3 / 0 |
v0.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.