h3
Minimal H(TTP) framework built for high performance and portability.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.d.cts | AI (source-diff): TypeScript declaration file with standard type definitions; long lines are normal for bundled .d.cts files, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.d.mts | AI (source-diff): TypeScript declaration file with standard type definitions; long lines are normal for bundled .d.mts files, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.d.ts | AI (source-diff): TypeScript declaration file with standard type definitions; long lines are normal for bundled .d.ts files, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): h3 is a well-established package (10.5M downloads/week, 3567 days old); not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): h3 is a well-established package (10.5M downloads/week, 3567 days old); not a typosquat of qs. | ai |
v1.15.11
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.