@whook/gcp-functions
Build and deploy to GCP Cloud Functions with Whook.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Active monorepo package; dormancy signal is a false positive for this well-established package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @types/qs is a TypeScript type-only package with no runtime risk. | ai | |
| phantom-deps | phantom-dep:@types/qs | AI (phantom-deps): Type-only package; not directly imported at runtime by design. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package; lack of provenance is consistent across all prior versions. | ai | |
| phantom-deps | phantom-dep:@whook/cors | AI (phantom-deps): Same org scope; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Config-file reference only; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:application-services | AI (phantom-deps): Config-file reference only; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:ajv-formats | AI (phantom-deps): Config-file reference only; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:ajv | AI (phantom-deps): Config-file reference only; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:camelcase | AI (phantom-deps): Config-file reference only; stable false positive for this framework package. | ai | |
| phantom-deps | phantom-dep:strict-qs | AI (phantom-deps): Config-file reference only; stable false positive for this framework package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 25.0.1 | 17 / 17 | |
| 25.0.0 | 17 / 17 | |
| 24.1.1 | 17 / 17 | |
| 24.1.0 | 17 / 17 | |
| 24.0.2 | 16 / 17 | |
| 24.0.1 | 16 / 17 | |
| 24.0.0 | 16 / 17 | |
| 23.0.0 | 16 / 16 | |
| 22.0.0 | 16 / 16 | |
| 21.0.1 | 16 / 16 | |
| 21.0.0 | 16 / 16 | |
| 20.1.2 | 16 / 17 | |
| 20.1.1 | 16 / 17 |
v25.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
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.