@f5xc-salesdemos/starlight-llms-txt
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:@types/hast | AI (phantom-deps): Type-only dep used by TypeScript toolchain, not directly imported at runtime; stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/micromatch | AI (phantom-deps): Type-only dep used by TypeScript toolchain, not directly imported at runtime; stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 12 / 3 | |
| 1.2.2 | 12 / 3 | |
| 1.2.1 | 12 / 3 | |
| 1.2.0 | 12 / 3 | |
| 1.1.0 | 12 / 3 | |
| 1.0.0 | 12 / 3 |
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.