lmdb-store-0.9 — Greenflagged

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

kriszyp

Keywords

lmdbdatabasemdblightning

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:nan	AI (phantom-deps): nan is a C++ addon helper used at compile time via binding.gyp, not imported in JS; phantom detection is a false positive for native addons.	ai	2026/04/24
install-scripts	install-script:install	AI (install-scripts): node-gyp-build is the standard install pattern for native addons shipping prebuilt binaries; stable and expected for this LMDB binding package.	ai	2026/04/24
npm-metadata	bundled-binaries	AI (npm-metadata): Prebuilt .node binaries for multiple platforms/ABIs are expected for this native LMDB binding; consistent with the package's documented purpose.	ai	2026/04/24

Versions (showing 4 of 4)

Version	Deps	Published
0.7.4	5 / 8	2020-12-04
0.7.3	5 / 8	2020-11-18
0.7.2	5 / 8	2020-11-01
0.7.1	5 / 8	2020-10-27

v0.7.4

3 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp-build

HIGH Bundled binary files (20) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/darwin-x64/electron.abi80.node • prebuilds/linux-x64/electron.abi80.node • prebuilds/win32-x64/electron.abi80.node • prebuilds/darwin-x64/electron.abi82.node • prebuilds/linux-x64/electron.abi82.node • prebuilds/win32-x64/electron.abi82.node • prebuilds/darwin-x64/node.abi57.node • prebuilds/linux-x64/node.abi57.node • prebuilds/win32-x64/node.abi57.node • prebuilds/darwin-x64/node.abi64.node ... and 10 more

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.

v0.7.3

3 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp-build

HIGH Bundled binary files (18) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/darwin-x64/electron.abi80.node • prebuilds/linux-x64/electron.abi80.node • prebuilds/win32-x64/electron.abi80.node • prebuilds/darwin-x64/electron.abi82.node • prebuilds/linux-x64/electron.abi82.node • prebuilds/win32-x64/electron.abi82.node • prebuilds/darwin-x64/node.abi57.node • prebuilds/linux-x64/node.abi57.node • prebuilds/win32-x64/node.abi57.node • prebuilds/darwin-x64/node.abi72.node ... and 8 more

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.

v0.7.2

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp-build

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.

v0.7.1

2 findings

HIGH Package has 'install' script install-scripts

Script: node-gyp-build

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.