@oracle/oraclejet-selenium-driver No license 28 versions

@oracle/oraclejet-selenium-driver

npm

28

Versions

—

License

No

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mvandervlietdmvjspeppertechcjbjkrismohanmilanvlacilkentarokinebuchihenrickyaubenknjingwuvic-nikmargabittotalamateurhourkarl-anthony-ngdrebolledannjoshimanish2788antoniofrucilfpvillegasmurselvaaseovicrhpatrickmgriccellilfeigenddsharpemig8447gek1bradtuckettwankevincflemminglesiachabanspavlusievavadimtroali.syedmeghana-vadlapallyvasaclucas.braunlmujumdarprabhuagkillianlynchpratiktiwarimbaadiejsefahwlouie-orclsmadeghe-orcl

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	2026/05/28
bogus-package	bogus-package	AI (bogus-package): Internal Oracle tooling package; missing metadata is expected for scoped enterprise packages.	ai	2026/05/18
npm-metadata	no-description	AI (npm-metadata): Internal Oracle tooling package; missing description is consistent across the OracleJET package family.	ai	2026/05/18

Versions (showing 28 of 28)

Version	Deps	Published
20.1.2	1 / 16	2026-06-01
20.1.1	1 / 16	2026-05-26
20.0.5	1 / 16	2026-05-28
20.0.4	1 / 16	2026-05-12
20.0.3	1 / 16	2026-04-30
20.0.2	1 / 16	2026-04-03
20.0.1	1 / 16	2026-03-18
20.0.0	1 / 16	2026-02-16
19.0.8	1 / 16	2026-05-28
19.0.7	1 / 16	2026-05-12
19.0.6	1 / 16	2026-05-01
19.0.5	1 / 16	2026-04-03
19.0.4	1 / 16	2026-03-18
19.0.3	1 / 16	2026-02-20
19.0.2	1 / 16	2026-01-21
19.0.1	1 / 16	2025-11-10
18.1.9	1 / 10	2026-05-27
18.1.8	1 / 10	2026-03-18
18.1.7	1 / 10	2026-02-19
18.1.6	1 / 10	2026-01-23
18.0.14	1 / 10	2026-05-27
18.0.13	1 / 10	2026-03-18
18.0.12	1 / 10	2026-02-21
18.0.11	1 / 10	2026-01-23
18.0.10	1 / 10	2025-11-25
17.1.9	1 / 4	2026-02-21
17.1.8	1 / 4	2025-12-20
17.0.11	1 / 4	2026-02-25

v20.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.1.1

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.4

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v20.0.3

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v20.0.2

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v20.0.1

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v20.0.0

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.7

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.6

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.5

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.4

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.3

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.2

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v19.0.1

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.1.9

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v18.1.8

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.1.7

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.1.6

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.0.14

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v18.0.13

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.0.12

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.0.11

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v18.0.10

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v17.1.9

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v17.1.8

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.

v17.0.11

2 findings

HIGH Unclaimed maintainer email domain: telety.io email-domain

Maintainer email '[email protected]' uses domain 'telety.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.