@hg-ts/http-controller
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all 149 versions; no provenance is the norm for this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Part of a large @hg-ts monorepo; sparse docs/keywords are a style choice, not spam/malware indicators. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package; missing description is a documentation gap, not a risk signal. | ai | |
| phantom-deps | phantom-dep:fastify-swagger | AI (phantom-deps): Declared as runtime dep but used via config; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 49 of 149)
| Version | Deps | Published |
|---|---|---|
| 0.1.112 | 4 / 21 | |
| 0.1.111 | 4 / 20 | |
| 0.1.110 | 4 / 20 | |
| 0.1.109 | 4 / 20 | |
| 0.1.108 | 4 / 20 | |
| 0.1.107 | 4 / 20 | |
| 0.1.106 | 4 / 20 | |
| 0.1.105 | 4 / 20 | |
| 0.1.104 | 4 / 20 | |
| 0.1.103 | 4 / 20 | |
| 0.1.102 | 4 / 20 | |
| 0.1.101 | 4 / 20 | |
| 0.1.100 | 4 / 20 | |
| 0.1.99 | 4 / 20 | |
| 0.1.98 | 4 / 20 | |
| 0.1.97 | 4 / 20 | |
| 0.1.96 | 4 / 19 | |
| 0.1.95 | 4 / 19 | |
| 0.1.94 | 4 / 19 | |
| 0.1.93 | 4 / 19 | |
| 0.1.88 | 4 / 19 | |
| 0.1.87 | 4 / 19 | |
| 0.1.86 | 4 / 19 | |
| 0.1.85 | 4 / 19 | |
| 0.1.84 | 4 / 19 | |
| 0.1.83 | 4 / 19 | |
| 0.1.82 | 4 / 19 | |
| 0.1.81 | 4 / 19 | |
| 0.1.80 | 4 / 19 | |
| 0.1.79 | 4 / 19 | |
| 0.1.78 | 4 / 19 | |
| 0.1.77 | 4 / 19 | |
| 0.1.76 | 4 / 19 | |
| 0.1.75 | 4 / 19 | |
| 0.1.74 | 4 / 19 | |
| 0.1.73 | 4 / 19 | |
| 0.1.72 | 4 / 19 | |
| 0.1.71 | 4 / 19 | |
| 0.1.70 | 4 / 19 | |
| 0.1.69 | 4 / 19 | |
| 0.1.68 | 4 / 19 | |
| 0.1.67 | 4 / 19 | |
| 0.1.66 | 4 / 19 | |
| 0.1.65 | 4 / 19 | |
| 0.1.64 | 4 / 19 | |
| 0.1.63 | 4 / 19 | |
| 0.1.61 | 4 / 19 | |
| 0.1.59 | 4 / 19 | |
| 0.1.58 | 4 / 19 |
v0.1.112
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.