@oracle/oraclejet-core-pack
JET core components fully implemented in VDOM
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): wlouie-orcl is an established Oracle org publisher with 45 approved packages; internal maintainer rotation. | ai | |
| dependencies | unvetted-dep:@oracle/oraclejet | AI (dependencies): First-party Oracle dependency; expected and stable for this package family across all versions. | ai | |
| source-diff | obfuscated-file:webdriver/docs/assets/search.js | AI (source-diff): TypeDoc-generated base64-encoded search index; standard documentation asset for this Oracle package. | ai | |
| source-diff | obfuscated-file:webdriver/docs/assets/navigation.js | AI (source-diff): TypeDoc-generated base64-encoded navigation data; standard documentation asset for this Oracle package. | ai | |
| source-diff | obfuscated-file:webdriver/docs/assets/main.js | AI (source-diff): TypeDoc-generated lunr.js search bundle; standard minified documentation asset for this Oracle package. | ai | |
| license | uncommon-license:UPL-1.0 | AI (license): UPL-1.0 is Oracle's standard open-source license used consistently across all Oracle JET packages. | ai | |
| provenance | no-provenance | AI (provenance): Established Oracle package family; provenance absence is consistent across all versions and not a meaningful risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 20.1.2 | 5 / 0 | |
| 20.1.1 | 5 / 0 | |
| 20.1.0 | 5 / 0 | |
| 20.0.5 | 5 / 0 | |
| 20.0.4 | 5 / 0 | |
| 20.0.3 | 5 / 0 | |
| 18.1.9 | 3 / 0 | |
| 18.0.14 | 3 / 0 |
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 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package 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.1.9
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.14
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.