@coasys/ad4m-react-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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is expected for internal workspace packages. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only dev dep for React hooks package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only dev dep; framework-scoped, loaded by convention in React projects. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 4 / 0 | |
| 0.11.1 | 5 / 0 | |
| 0.11.0 | 5 / 0 | |
| 0.10.1 | 5 / 0 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.