@oracle/oraclejet-testing
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 | publisher-changed | AI (provenance): Oracle-org internal maintainer rotation; new publisher has clean track record within the same org. | ai | |
| email-domain | unclaimed-email:telety.io | AI (email-domain): Established Oracle package; email domain issue is a metadata concern but no other malicious signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Oracle internal package; sparse metadata is consistent across the oraclejet monorepo, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Oracle monorepo package; missing description is a metadata style choice, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for enterprise/internal packages; not a risk signal here. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 20.1.3 | 0 / 14 | |
| 20.1.2 | 0 / 14 | |
| 20.1.1 | 0 / 14 | |
| 20.1.0 | 0 / 14 | |
| 20.0.6 | 0 / 14 | |
| 20.0.5 | 0 / 14 | |
| 20.0.4 | 0 / 14 | |
| 20.0.3 | 0 / 14 | |
| 20.0.2 | 0 / 14 | |
| 20.0.1 | 0 / 14 | |
| 20.0.0 | 0 / 14 | |
| 19.0.8 | 0 / 14 | |
| 19.0.7 | 0 / 14 | |
| 19.0.6 | 0 / 14 | |
| 19.0.5 | 0 / 14 | |
| 19.0.4 | 0 / 14 | |
| 19.0.3 | 0 / 14 | |
| 19.0.2 | 0 / 14 | |
| 19.0.1 | 0 / 14 | |
| 18.1.10 | 0 / 4 | |
| 18.1.9 | 0 / 4 | |
| 18.1.8 | 0 / 4 | |
| 18.1.7 | 0 / 4 | |
| 18.1.6 | 0 / 4 | |
| 18.0.15 | 0 / 4 | |
| 18.0.14 | 0 / 4 | |
| 18.0.13 | 0 / 4 | |
| 18.0.12 | 0 / 4 | |
| 18.0.11 | 0 / 4 | |
| 18.0.10 | 0 / 4 | |
| 17.1.9 | 0 / 4 | |
| 17.1.8 | 0 / 4 | |
| 17.0.11 | 0 / 4 |
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.
v18.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.