oracledb
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 |
|---|---|---|---|---|
| install-scripts | install-script:install | AI (install-scripts): oracledb's install script selects and loads prebuilt platform-specific native binaries — this is Oracle's documented and stable install flow for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): oracledb ships prebuilt .node binaries for multiple platforms as part of its documented distribution model; these are not backdoors. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used in a config-provider password decoding path with an explicit developer warning; not obfuscation or malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used in TNS protocol constants (e.g. OID byte sequences); standard Oracle network protocol implementation, not malicious. | ai |
v6.10.0
3 findingsScript: node package/install.js
Package contains compiled binaries that could be backdoors: • build/Release/oracledb-6.10.0-darwin-arm64.node • build/Release/oracledb-6.10.0-darwin-x64.node • build/Release/oracledb-6.10.0-linux-arm64.node • build/Release/oracledb-6.10.0-linux-x64.node • build/Release/oracledb-6.10.0-win32-x64.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.