@eui/core
eUI core package - holding UI components for Desktop applications
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:types/eui-core.d.ts | AI (source-diff): Large auto-generated TS typings file, not obfuscated code. | ai | |
| source-diff | net-exec-file:docs/js/libs/jszip.min.js | AI (source-diff): Bundled well-known JSZip library, not malicious code. | ai | |
| source-diff | net-exec-file:docs/js/libs/vis-network.min.js | AI (source-diff): Bundled well-known vis-network library, not malicious code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established institutional UI package, not spam. | ai | |
| source-diff | net-exec-file:docs/js/libs/vis.min.js | AI (source-diff): vis.min.js is the canonical vis.js 4.21.0 UMD bundle; network+exec pattern is standard module loading, not malware. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known Angular/TypeScript implicit runtime dep; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped EU Commission Angular UI library; name similarity to 'cors' is coincidental, not a squatting attempt. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 21.4.0 | 1 / 0 | |
| 21.3.3 | 1 / 0 | |
| 21.3.2 | 1 / 0 | |
| 21.3.1 | 1 / 0 | |
| 21.3.0 | 1 / 0 | |
| 21.2.6 | 1 / 0 | |
| 21.2.5 | 1 / 0 | |
| 21.2.4 | 1 / 0 | |
| 21.2.3 | 1 / 0 | |
| 21.2.2 | 1 / 0 | |
| 21.2.1 | 1 / 0 | |
| 21.2.0 | 1 / 0 | |
| 21.1.1 | 1 / 0 | |
| 21.1.0 | 1 / 0 | |
| 21.0.4 | 1 / 0 | |
| 21.0.3 | 1 / 0 | |
| 21.0.2 | 1 / 0 | |
| 21.0.1 | 1 / 0 | |
| 19.3.17 | 1 / 0 | |
| 19.3.16 | 1 / 0 | |
| 19.3.15 | 1 / 0 | |
| 19.3.14 | 1 / 0 | |
| 19.3.13 | 1 / 0 | |
| 19.3.12 | 1 / 0 | |
| 19.3.11 | 1 / 0 | |
| 19.3.10 | 1 / 0 | |
| 19.3.9 | 1 / 0 | |
| 19.3.8 | 1 / 0 |
v21.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.3.3
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.2.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.4
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.3
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.2
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.1
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.13
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 (rambou) than the most recent previously approved version (ec.europa.eui) on 2026-03-12, but rambou 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.
v19.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.