@api-hooks/bp
React hooks for the Bundlephobia API, built on @tanstack/react-query
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small utility package; missing provenance is a hygiene issue, not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:bundlephobia-api-client | AI (phantom-deps): bundlephobia-api-client is the core runtime dep; phantom-dep fires due to dual listing in deps and devDeps, not a real missing import. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @api-hooks/bp; 'bp' abbreviates bundlephobia, not a typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @api-hooks/bp; 'bp' abbreviates bundlephobia, not a typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @api-hooks/bp; 'bp' abbreviates bundlephobia, not a typosquat of yup. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.3.1 | 1 / 10 | |
| 2.3.0 | 1 / 10 | |
| 2.2.0 | 1 / 10 | |
| 2.1.0 | 1 / 10 | |
| 2.0.0 | 1 / 10 | |
| 1.9.0 | 1 / 10 | |
| 1.6.0 | 1 / 10 | |
| 1.4.0 | 1 / 10 | |
| 1.3.0 | 1 / 10 | |
| 1.2.4 | 1 / 10 | |
| 1.2.2 | 1 / 10 | |
| 1.2.1 | 1 / 10 | |
| 1.2.0 | 1 / 10 | |
| 1.1.0 | 1 / 10 | |
| 1.0.0 | 1 / 10 |
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.