@buildeross/hooks
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 | net-exec-file:dist/useInvoiceData.js | AI (source-diff): Bundled lodash 4.17.21 inlined by tsup; not malware. | ai | |
| source-diff | net-exec-file:dist/chunk-2FS57TMP.mjs | AI (source-diff): Bundled lodash 4.17.21 inlined by tsup; not malware. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by lodash being bundled into dist by tsup. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Token parsing pattern in useDaoAuction.ts; decodes a JWT-like token substring, not a hidden payload. | ai | |
| dependencies | unvetted-dep:@zoralabs/coins-sdk | AI (dependencies): @zoralabs/coins-sdk is the official Zora protocol SDK; legitimate dependency for this hooks package. | ai | |
| provenance | no-provenance | AI (provenance): Monorepo package without provenance attestation; no other risk signals present. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 3 / 23 | |
| 0.3.1 | 3 / 23 | |
| 0.3.0 | 3 / 23 | |
| 0.2.2 | 2 / 21 | |
| 0.2.1 | 2 / 21 | |
| 0.2.0 | 2 / 21 | |
| 0.1.3 | 6 / 8 | |
| 0.1.2 | 6 / 8 | |
| 0.1.1 | 6 / 8 | |
| 0.1.0 | 6 / 8 |
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.