@whook/authorization
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@whook/whook | AI (dependencies): Same-monorepo sibling dep from the same trusted publisher; not an independent risk. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package with clean history; provenance absence is consistent across all versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 25.0.0 | 6 / 16 | |
| 24.1.1 | 6 / 16 | |
| 24.1.0 | 6 / 16 | |
| 24.0.1 | 6 / 16 | |
| 24.0.0 | 6 / 16 | |
| 23.0.0 | 6 / 16 | |
| 22.0.0 | 6 / 16 | |
| 21.0.1 | 6 / 16 | |
| 21.0.0 | 6 / 16 | |
| 20.1.2 | 6 / 17 |
v25.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.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.
v20.1.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.