@journeyapps/sqlcipher
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publish moved to GitHub Actions CI with SLSA attestation; legitimate automation change for this package. | ai | |
| provenance | missing-githead | AI (provenance): GitHub Actions CI publish via Sigstore/SLSA replaces gitHead; provenance attestation covers the gap. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): `bindings` is a well-known, stable native-addon helper replacing node-pre-gyp; not a supply-chain risk. | ai | |
| install-scripts | install-script:install | AI (install-scripts): Standard node-pre-gyp prebuilt binary fetch; stable and expected for this native binding package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads the resolved native binding path via node-pre-gyp; standard pattern for native addons, not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a build-time dependency used in binding.gyp/native build, not directly imported in JS. | ai |
v6.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
2 findingsScript: node-pre-gyp install --fallback-to-build
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.