← Home

@whook/create

npm Repository Homepage

Kickstart a new Whook server

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

nfroidure

Keywords

whookknifecycleRESTHTTPOpenAPIwebservicecreator

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-lived package from trusted publisher with clean diff; dormancy likely reflects maintenance cadence, not takeover. ai
dependencies unvetted-dep:knifecycle AI (dependencies): Core dependency of the whook ecosystem by the same author; stable across versions. ai
dependencies unvetted-dep:common-services AI (dependencies): Core dependency of the whook ecosystem by the same author; stable across versions. ai
phantom-deps phantom-dep:@inquirer/prompts AI (phantom-deps): Declared runtime dep used in the CLI binary; phantom-dep heuristic fires because it's not directly imported in src. ai
phantom-deps phantom-dep:@whook/example AI (phantom-deps): Same-org sibling used as template/example source; not a direct code import, stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
25.0.0 9 / 16
24.1.1 9 / 16
24.1.0 9 / 16
24.0.2 9 / 16
24.0.1 9 / 16
24.0.0 9 / 16
23.0.0 9 / 16
22.0.0 9 / 16
21.0.1 9 / 16
21.0.0 9 / 16
20.1.2 9 / 17
20.1.1 9 / 17

v25.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v23.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v21.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v21.0.0

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.