@oracle/oraclejet-selenium-driver
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 |
|---|---|---|---|---|
| email-domain | unclaimed-email:telety.io | AI (email-domain): Package is under @oracle scope with established publisher track record; email domain risk is low in this context. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Oracle tooling package; missing metadata is expected for scoped enterprise packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal Oracle tooling package; missing description is consistent across the OracleJET package family. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 20.1.3 | 1 / 16 | |
| 20.1.2 | 1 / 16 | |
| 20.1.1 | 1 / 16 | |
| 20.0.6 | 1 / 16 | |
| 20.0.5 | 1 / 16 | |
| 20.0.4 | 1 / 16 | |
| 20.0.3 | 1 / 16 | |
| 20.0.2 | 1 / 16 | |
| 20.0.1 | 1 / 16 | |
| 20.0.0 | 1 / 16 | |
| 19.0.8 | 1 / 16 | |
| 19.0.7 | 1 / 16 | |
| 19.0.6 | 1 / 16 | |
| 19.0.5 | 1 / 16 | |
| 19.0.4 | 1 / 16 | |
| 19.0.3 | 1 / 16 | |
| 19.0.2 | 1 / 16 | |
| 19.0.1 | 1 / 16 | |
| 18.1.10 | 1 / 10 | |
| 18.1.9 | 1 / 10 | |
| 18.1.8 | 1 / 10 | |
| 18.1.7 | 1 / 10 | |
| 18.1.6 | 1 / 10 | |
| 18.0.15 | 1 / 10 | |
| 18.0.14 | 1 / 10 | |
| 18.0.13 | 1 / 10 | |
| 18.0.12 | 1 / 10 | |
| 18.0.11 | 1 / 10 | |
| 18.0.10 | 1 / 10 | |
| 17.1.9 | 1 / 4 | |
| 17.1.8 | 1 / 4 | |
| 17.0.11 | 1 / 4 |
v20.1.3
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.15
2 findingsPackage 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.