@clr/addons
Addons for Clarity
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:esm2020/datagrid-filters/advanced-filters/users-filter.component.mjs | AI (source-diff): Angular AOT compiler output with long inlined templates; not obfuscated. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-addons-datagrid-filters.mjs | AI (source-diff): Standard Angular FESM2022 bundle; long lines are bundler output, not obfuscation. | ai | |
| source-diff | obfuscated-file:fesm2022/clr-addons-datagrid.mjs | AI (source-diff): Standard Angular FESM2022 bundle; long lines are bundler output, not obfuscation. | ai | |
| source-diff | obfuscated-file:types/clr-addons-datagrid.d.ts | AI (source-diff): TypeScript declaration file with long union types; not obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known Angular/TypeScript runtime implicit dependency injected by the bundler. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 18.1.0 | 1 / 0 | |
| 17.13.0 | 1 / 0 | |
| 17.12.4 | 1 / 0 | |
| 17.12.3 | 1 / 0 | |
| 17.12.2 | 1 / 0 | |
| 17.12.1 | 1 / 0 | |
| 17.12.0 | 1 / 0 |
v18.1.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.12.4
3 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.
This version was published by a different npm account (danieltsanev) than the most recent previously approved version (clarity-service-account) on 2026-03-30, 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.3
3 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.
This version was published by a different npm account (danieltsanev) than the most recent previously approved version (clarity-service-account) on 2026-03-30, 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.
v17.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v17.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.