← Home

oracledb

5
Versions
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

krismohananthony.tuiningasharadchan87

Keywords

OracleDatabaseofficialDBSQLJSONPL/SQLSODAOCIAPIclientlibrarydriveradd-onextensionbindinginterfaceadaptermodule

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Config provider loader, fixed known set, not attacker-controlled. ai
maintainer-change maintainer-removed AI (maintainer-change): Oracle corporate account consolidation; package is official Oracle driver with consistent repo/metadata. ai
publish-pattern dormant-publish AI (publish-pattern): Long-established Oracle package; dormancy reflects release cadence, not account takeover. ai
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
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
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

Versions (showing 5 of 5)

Version Deps Published
7.0.0 0 / 0
6.10.0 0 / 0
6.9.0 0 / 0
6.6.0 0 / 0
6.5.1 0 / 0

v6.6.0

1 finding
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.

v6.5.1

1 finding
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.