@longzai-intelligence/http-utils
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:@longzai-intelligence/http-utils-preset-node | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; declared-but-not-directly-imported is expected. | ai | |
| phantom-deps | phantom-dep:@longzai-intelligence/http-utils-preset-browser | AI (phantom-deps): Umbrella package re-exports same-org sub-packages; declared-but-not-directly-imported is expected. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.0.19 | 7 / 16 | |
| 0.0.18 | 7 / 16 | |
| 0.0.17 | 7 / 16 | |
| 0.0.16 | 7 / 16 | |
| 0.0.15 | 7 / 16 | |
| 0.0.14 | 7 / 16 | |
| 0.0.13 | 7 / 16 | |
| 0.0.12 | 7 / 16 | |
| 0.0.11 | 7 / 16 | |
| 0.0.10 | 7 / 16 | |
| 0.0.9 | 7 / 16 | |
| 0.0.8 | 7 / 16 | |
| 0.0.7 | 7 / 16 | |
| 0.0.6 | 7 / 16 | |
| 0.0.5 | 7 / 16 | |
| 0.0.4 | 7 / 16 | |
| 0.0.3 | 7 / 16 | |
| 0.0.2 | 7 / 16 | |
| 0.0.1 | 3 / 16 |
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.