lmdb
Simple, efficient, scalable, high-performance LMDB interface
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): yarn added as runtime dep appears to be a build tooling artifact; not imported at runtime per phantom-dep finding. | ai | |
| phantom-deps | phantom-dep:yarn | AI (phantom-deps): yarn added as runtime dep for CLI use in prebuild scripts, not imported as a module; stable false positive for this package. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): The fetch() call in mod.ts is a Deno-specific fallback to download prebuilt native binaries — standard pattern for cross-runtime native bindings, not telemetry or exfiltration. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): lmdb is a native LMDB binding; prebuilt .node binaries for multiple platforms/ABIs/electron targets are its standard distribution mechanism via prebuildify. | ai | |
| dependencies | unvetted-dep:node-gyp-build | AI (dependencies): node-gyp-build is the standard prebuild loader for native addons; canonical dependency for this package. | ai | |
| phantom-deps | phantom-dep:nan | AI (phantom-deps): nan is used by the C++ addon layer via binding.gyp, not directly imported in JS; expected for native addons. | ai | |
| phantom-deps | phantom-dep:@lmdb/lmdb-linux-arm64 | AI (phantom-deps): Platform-specific prebuilt binary package; loaded at runtime by node-gyp-build, not directly imported in JS. | ai | |
| install-scripts | install-script:install | AI (install-scripts): lmdb is a native addon; node-gyp-build-optional-packages is the standard mechanism for loading prebuilt platform binaries. Stable and expected for this package. | ai | |
| phantom-deps | phantom-dep:@lmdb/lmdb-darwin-arm64 | AI (phantom-deps): Platform-specific prebuilt binary package; loaded at runtime by node-gyp-build, not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:node-addon-api | AI (phantom-deps): node-addon-api is a build-time C++ addon dependency referenced in gyp config, not a runtime JS import. Expected for native addons. | ai | |
| phantom-deps | phantom-dep:@lmdb/lmdb-linux-arm | AI (phantom-deps): Platform-specific prebuilt binary package; loaded at runtime by node-gyp-build, not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@lmdb/lmdb-linux-x64 | AI (phantom-deps): Platform-specific prebuilt binary package; loaded at runtime by node-gyp-build, not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@lmdb/lmdb-win32-x64 | AI (phantom-deps): Platform-specific prebuilt binary package; loaded at runtime by node-gyp-build, not directly imported in JS. | ai | |
| phantom-deps | phantom-dep:@lmdb/lmdb-darwin-x64 | AI (phantom-deps): Platform-specific prebuilt binary package; loaded at runtime by node-gyp-build, not directly imported in JS. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 3.5.2 | 6 / 13 | |
| 3.4.4 | 5 / 12 | |
| 3.4.2 | 5 / 12 | |
| 3.1.0 | 5 / 12 | |
| 3.0.12 | 5 / 12 | |
| 3.0.4 | 5 / 12 | |
| 3.0.0 | 5 / 12 | |
| 2.9.2 | 5 / 12 | |
| 2.9.1 | 5 / 12 | |
| 2.8.5 | 11 / 12 | |
| 2.8.4 | 11 / 11 | |
| 2.8.0 | 12 / 11 | |
| 2.7.5 | 11 / 11 | |
| 2.7.3 | 11 / 11 | |
| 2.7.1 | 11 / 11 | |
| 2.6.7 | 11 / 11 | |
| 2.5.3 | 11 / 10 | |
| 2.5.1 | 11 / 10 | |
| 2.2.5 | 5 / 10 | |
| 2.2.4 | 5 / 10 | |
| 2.2.3 | 5 / 10 | |
| 2.1.7 | 5 / 10 | |
| 2.1.5 | 5 / 11 | |
| 2.0.0 | 5 / 11 | |
| 1.6.13 | 5 / 10 | |
| 1.6.12 | 5 / 10 | |
| 1.6.10 | 5 / 10 | |
| 1.6.9 | 5 / 11 | |
| 1.6.8 | 6 / 11 | |
| 1.6.7 | 6 / 9 | |
| 1.6.6 | 6 / 9 | |
| 1.6.4 | 6 / 9 | |
| 1.6.3 | 6 / 9 | |
| 1.6.2 | 6 / 9 | |
| 1.6.1 | 6 / 9 | |
| 1.6.0 | 6 / 9 | |
| 1.5.5 | 5 / 9 | |
| 1.5.4 | 5 / 9 | |
| 0.2.0 | 2 / 3 | |
| 0.1.3 | 2 / 3 | |
| 0.1.2 | 2 / 3 | |
| 0.1.1 | 2 / 3 | |
| 0.1.0 | 2 / 3 | |
| 0.0.3 | 1 / 3 | |
| 0.0.2 | 1 / 3 | |
| 0.0.1 | 1 / 3 | |
| 0.0.0 | 3 / 1 |
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
2 findingsScript: node-gyp-build-optional-packages
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/darwin-arm64/electron.abi99.glibc.node • prebuilds/darwin-x64/electron.abi99.glibc.node • prebuilds/linux-arm64/electron.abi99.glibc.node • prebuilds/linux-x64/electron.abi99.glibc.node • prebuilds/linux-arm64/electron.abi99.musl.node • prebuilds/linux-x64/electron.abi99.musl.node • prebuilds/win32-x64/electron.abi99.node • prebuilds/darwin-arm64/node.abi102.glibc.node • prebuilds/darwin-x64/node.abi102.glibc.node • prebuilds/linux-arm64/node.abi102.glibc.node ... and 32 more
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
2 findingsPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.