@hestia-earth/glossary
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Pattern is a scoped resource loader under ./resources/; not arbitrary module loading. Stable across versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.93.0 | 0 / 11 | |
| 0.92.1 | 0 / 11 | |
| 0.92.0 | 0 / 11 | |
| 0.91.1 | 0 / 11 | |
| 0.91.0 | 0 / 11 | |
| 0.90.0 | 0 / 11 |
v0.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.90.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.