@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, so a manually published version cannot be tied back to a reviewed commit.
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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 20.1.3 | 2 / 19 | |
| 20.1.2 | 2 / 19 | |
| 20.1.1 | 2 / 19 | |
| 20.1.0 | 2 / 19 | |
| 20.0.6 | 2 / 19 | |
| 20.0.5 | 2 / 19 | |
| 20.0.4 | 2 / 19 | |
| 20.0.3 | 2 / 19 | |
| 20.0.2 | 2 / 19 | |
| 20.0.1 | 2 / 19 | |
| 20.0.0 | 2 / 19 | |
| 18.0.15 | 1 / 16 | |
| 18.0.14 | 1 / 16 | |
| 18.0.13 | 1 / 16 | |
| 18.0.12 | 1 / 16 | |
| 18.0.11 | 1 / 16 | |
| 18.0.10 | 1 / 16 | |
| 17.1.9 | 1 / 14 | |
| 17.1.8 | 1 / 14 | |
| 17.0.11 | 1 / 14 |
v20.1.3
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 (meghana-vadlapally) than the most recent previously approved version (smadeghe-orcl) on 2026-07-15, but meghana-vadlapally 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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.0.2
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 (meghana-vadlapally) than the most recent previously approved version (wlouie-orcl) on 2026-04-03, but meghana-vadlapally 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.1
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 (smadeghe-orcl) on 2026-03-18, 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.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 (smadeghe-orcl) on 2026-02-16, 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.
v18.0.15
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 (smadeghe-orcl) than the most recent previously approved version (meghana-vadlapally) on 2026-07-09, but smadeghe-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.
v18.0.13
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 (meghana-vadlapally) than the most recent previously approved version (wlouie-orcl) on 2026-03-18, but meghana-vadlapally 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.
v18.0.12
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 (smadeghe-orcl) than the most recent previously approved version (wlouie-orcl) on 2026-02-21, but smadeghe-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.
v18.0.11
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 (smadeghe-orcl) on 2026-01-23, 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.
v18.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.1.9
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 (smadeghe-orcl) than the most recent previously approved version (wlouie-orcl) on 2026-02-21, but smadeghe-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.
v17.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.0.11
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 (smadeghe-orcl) on 2026-02-25, 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.