@clr/angular
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:fesm2022/clr-angular-modal.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-icon.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-layout-breadcrumbs.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-accordion.mjs | AI (source-diff): Standard Angular fesm2022 compiler output; long lines are normal for this build format. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-button.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-data-datagrid.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-data-tree-view.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-angular-forms-combobox.mjs | AI (source-diff): Standard Angular fesm2022 compiler output. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency; phantom-dep false positive for this package. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in Angular template context proxy — standard framework pattern, not obfuscation. | ai |
v18.1.0
9 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.
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.
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.
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.
v17.13.0
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 (danieltsanev) than the most recent previously approved version (clarity-service-account) on 2026-04-14, but danieltsanev 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.
v17.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.