@whook/dev
Whook development dependencies.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ts-morph | AI (phantom-deps): ts-morph is a build/config dependency; correctly declared and used in metapak/build context. | ai | |
| dependencies | unvetted-dep:knifecycle | AI (dependencies): Core dependency of the whook ecosystem maintained by the same author. | ai | |
| dependencies | unvetted-dep:@whook/whook | AI (dependencies): Same monorepo package; stable ecosystem dependency. | ai | |
| dependencies | unvetted-dep:common-services | AI (dependencies): Established companion package by same author. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @whook/dev package; Levenshtein match to 'ajv' is a false positive with no real similarity. | ai | |
| dependencies | unvetted-dep:ya-open-api-types | AI (dependencies): OpenAPI types package in the same ecosystem; no risk signals. | ai | |
| dependencies | unvetted-dep:esbuild-node-externals | AI (dependencies): Popular esbuild utility plugin; well-known in the ecosystem. | ai | |
| dependencies | unvetted-dep:schema2dts | AI (dependencies): Known utility by same author; no risk signals. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 25.0.0 | 15 / 17 | |
| 24.1.0 | 15 / 17 | |
| 24.0.2 | 15 / 17 | |
| 24.0.1 | 15 / 17 | |
| 24.0.0 | 15 / 17 | |
| 23.0.0 | 15 / 17 |
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.