@whook/example
A basic Whook server
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo with coordinated releases; long gaps between releases are normal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 141 versions; lack of provenance is consistent across all prior releases. | ai | |
| phantom-deps | phantom-dep:strict-qs | AI (phantom-deps): strict-qs is a declared runtime dependency; phantom-dep heuristic misfires on this package's import style. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 25.0.0 | 15 / 22 | |
| 24.1.1 | 15 / 22 | |
| 24.1.0 | 15 / 22 | |
| 24.0.2 | 15 / 22 | |
| 24.0.1 | 15 / 22 | |
| 24.0.0 | 15 / 22 | |
| 23.0.0 | 15 / 21 | |
| 22.0.0 | 15 / 21 | |
| 21.0.1 | 15 / 21 | |
| 21.0.0 | 15 / 21 | |
| 20.1.2 | 15 / 22 | |
| 20.1.1 | 15 / 22 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.0
1 findingPackage 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.
v20.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.