@eui/ecl
eUI ECL components package
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:fesm2022/eui-ecl-components-ecl-quiz.mjs | AI (source-diff): Long-line heuristic false positive on readable Angular build output, not true obfuscation. | ai | |
| source-diff | net-exec-file:docs/js/libs/vis.min.js | AI (source-diff): Known vis.js library bundled in docs; minified bundler output, not a dropper. | ai | |
| source-diff | obfuscated-file:components/ecl-all/ecl-all.module.d.ts | AI (source-diff): Angular .d.ts with long import lists; not obfuscation. | ai | |
| source-diff | net-exec-file:docs/js/libs/jszip.min.js | AI (source-diff): Bundled third-party jszip library in docs assets; no malicious behavior in sample. | ai | |
| source-diff | net-exec-file:docs/js/libs/vis-network.min.js | AI (source-diff): Bundled third-party vis-network library in docs assets; standard UMD bundle. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit Angular/TS runtime dependency. | 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
2 findingsNewly 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
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.
Package 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-13, 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.
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.15
3 findingsNewly 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.
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.