@primate/htmx
HTMX for Primate
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:htmx-esm | AI (phantom-deps): htmx-esm is used via config/runtime resolution, not direct import; consistent with this package's module pattern. | ai | |
| phantom-deps | phantom-dep:@rcompat/html | AI (phantom-deps): Part of the rcompat ecosystem used via config/runtime resolution; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rcompat/assert | AI (phantom-deps): Part of the rcompat ecosystem used via config/runtime resolution; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rcompat/fs | AI (phantom-deps): Declared as a runtime dependency in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rcompat/is | AI (phantom-deps): Declared as a runtime dependency in package.json; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rcompat/runtime | AI (phantom-deps): Declared as a runtime dependency in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.26.0 | 9 / 0 | |
| 0.25.0 | 9 / 0 | |
| 0.24.0 | 7 / 1 | |
| 0.22.0 | 8 / 0 |
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.