@gcforms/database
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Prisma-generated WASM loader pattern; decodes bundled query engine binary, not a malicious payload. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package from Canadian Digital Service; no public repo/description expected for org-internal DB library. | ai | |
| phantom-deps | phantom-dep:pg | AI (phantom-deps): pg is a runtime dep used via Prisma adapter; may not be directly imported in source but is a legitimate declared dependency. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 4 / 7 | |
| 1.0.6 | 4 / 7 | |
| 1.0.5 | 4 / 7 | |
| 1.0.4 | 3 / 7 | |
| 1.0.3 | 3 / 7 | |
| 1.0.2 | 3 / 7 | |
| 1.0.1 | 3 / 7 | |
| 1.0.0 | 3 / 7 |
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.