lmdb-store
Simple, efficient, scalable data store wrapper for LMDB
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:node-lmdb | AI (dependencies): node-lmdb is the canonical native LMDB binding for Node.js and is the expected core dependency for this LMDB wrapper package. Stable across all versions. | ai | |
| dependencies | unvetted-dep:lmdb-store-0.9 | AI (dependencies): lmdb-store-0.9 is a prior version of the same package used as a dependency for compatibility/migration; this is an intentional and stable pattern for this package. | ai | |
| source-diff | encoded-string-file:test/index.test.js | AI (source-diff): The 'encoded' string is a 255-char ASCII test fixture in a test file, used to verify lmdb-store handles max-length strings. Not a payload or obfuscated code. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ordered-binary is a legitimate utility for binary-sortable key encoding, consistent with lmdb-store's ordered key-value storage use case. | ai | |
| provenance | no-provenance | AI (provenance): Established package published long before Sigstore provenance was available on npm; absence of attestation is not a risk signal for this publisher. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is the standard tool for loading prebuilt native binaries in Node.js addons; its use here is expected and appropriate for lmdb-store. | ai | |
| install-scripts | install-script:install | AI (install-scripts): lmdb-store is a native LMDB addon; node-gyp-build install script is the standard mechanism for loading prebuilt binaries. Stable for this package. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is used in the native C++ addon build (binding.gyp), not imported in JS. This is the standard usage pattern for NAN-based native addons. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt .node binaries for multiple platforms/ABIs are expected for a native addon like lmdb-store. Consistent with the package's documented build process. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 8 | |
| 1.6.14 | 5 / 10 | |
| 1.6.2 | 6 / 9 | |
| 1.6.1 | 6 / 9 | |
| 1.5.6 | 5 / 10 | |
| 1.4.2 | 5 / 9 | |
| 1.4.0 | 5 / 9 | |
| 1.3.2 | 5 / 9 | |
| 1.3.1 | 5 / 9 | |
| 1.2.0 | 5 / 9 | |
| 1.1.11 | 5 / 9 | |
| 1.1.4 | 5 / 9 | |
| 0.9.12 | 6 / 9 | |
| 0.9.10 | 6 / 9 | |
| 0.9.5 | 6 / 9 | |
| 0.9.4 | 6 / 9 | |
| 0.9.1 | 6 / 9 | |
| 0.9.0 | 6 / 9 | |
| 0.8.8 | 6 / 8 | |
| 0.8.7 | 6 / 8 | |
| 0.8.5 | 6 / 8 | |
| 0.8.4 | 6 / 8 | |
| 0.8.3 | 6 / 8 | |
| 0.8.2 | 6 / 8 | |
| 0.8.1 | 6 / 8 | |
| 0.3.24 | 2 / 3 |
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.14
3 findingsScript: node-gyp-build
Package contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/electron.abi98.node • prebuilds/darwin-x64/electron.abi98.node • prebuilds/linux-arm64/electron.abi98.node • prebuilds/linux-x64/electron.abi98.node • prebuilds/win32-x64/electron.abi98.node • prebuilds/linux-x64/node.abi102.musl.node • prebuilds/darwin-arm64/node.abi102.node • prebuilds/darwin-x64/node.abi102.node • prebuilds/linux-arm64/node.abi102.node • prebuilds/linux-x64/node.abi102.node ... and 20 more
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.