better-sqlite3-multiple-ciphers
2
Versions
—
License
Yes
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
m4heshd
Keywords
sqlsqlitesqlite3sqleetsqlciphersqlite3multipleciphersencryptiontransactionsuser-defined functionsaggregate functionswindow functionsdatabase
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): Canonical native binding install: prebuild-install with node-gyp fallback; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:prebuild-install | AI (phantom-deps): prebuild-install is a declared dependency used implicitly via install script; not a real phantom dep. | ai |
v12.10.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.9.0
2 findings
HIGH
Package has 'install' script
install-scripts
Script: prebuild-install || node-gyp rebuild --release
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.