@oracle/oraclejet-webdriver
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Oracle package; provenance is a best-practice signal, not a blocker for this mature namespace. | ai | |
| dependencies | unvetted-dep:@oracle/oraclejet | AI (dependencies): First-party Oracle dependency in the OracleJET suite; expected and stable across versions. | ai | |
| dependencies | unvetted-dep:@oracle/oraclejet-selenium-driver | AI (dependencies): First-party Oracle dependency in the OracleJET suite; expected and stable across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 20.1.2 | 2 / 19 | |
| 20.1.1 | 2 / 19 | |
| 20.1.0 | 2 / 19 | |
| 20.0.5 | 2 / 19 | |
| 20.0.4 | 2 / 19 | |
| 20.0.3 | 2 / 19 | |
| 18.0.14 | 1 / 16 |
v20.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (wlouie-orcl) than the most recent previously approved version (meghana-vadlapally) on 2026-05-19, but wlouie-orcl is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v20.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.