@taiga-ui/cdk
Base library for creating Angular components and applications using Taiga UI principles regarding of actual visual appearance
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): vladimir.potekhin is a listed contributor in package.json with strong approval track record; transition appears legitimate. | ai | |
| source-diff | obfuscated-file:esm2022/directives/active-zone/active-zone.directive.mjs | AI (source-diff): Standard Angular compiled directive with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/directives/animated/animated.directive.mjs | AI (source-diff): Standard Angular compiled directive with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/directives/auto-focus/autofocus.directive.mjs | AI (source-diff): Standard Angular compiled directive with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/directives/auto-focus/autofocus.options.mjs | AI (source-diff): Inline base64 sourcemap causes long line; code is plaintext Angular DI configuration. | ai | |
| source-diff | obfuscated-file:esm2022/classes/control.mjs | AI (source-diff): Standard Angular compiled class with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/date-time/day-range.mjs | AI (source-diff): Readable date utility class; long lines from inline sourcemap. | ai | |
| source-diff | obfuscated-file:esm2022/tokens/active-element.mjs | AI (source-diff): Long lines caused by inline sourcemaps in standard Angular library build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/directives/auto-focus/handlers/default.handler.mjs | AI (source-diff): Standard Angular handler with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/utils/miscellaneous/directive-binding.mjs | AI (source-diff): Standard Angular utility with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/observables/drag-and-drop-from.mjs | AI (source-diff): Standard Angular observable with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/directives/droppable/droppable.directive.mjs | AI (source-diff): Standard Angular directive with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/tokens/environment.mjs | AI (source-diff): Standard Angular token with inline sourcemap; not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/date-time/day.mjs | AI (source-diff): Readable date utility class; long lines from inline sourcemap. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 5.9.0 | 1 / 0 | |
| 5.8.0 | 1 / 0 | |
| 5.7.0 | 1 / 0 | |
| 5.6.0 | 1 / 0 | |
| 5.5.0 | 1 / 0 | |
| 5.4.0 | 1 / 0 | |
| 5.3.0 | 1 / 0 | |
| 5.2.0 | 1 / 0 | |
| 5.1.0 | 1 / 0 | |
| 5.0.0 | 1 / 0 | |
| 4.85.0 | 1 / 0 | |
| 4.84.0 | 1 / 0 | |
| 4.83.0 | 1 / 0 | |
| 4.82.0 | 1 / 0 | |
| 4.81.0 | 1 / 0 | |
| 4.80.1 | 1 / 0 | |
| 4.80.0 | 1 / 0 | |
| 4.79.0 | 1 / 0 | |
| 4.78.1 | 1 / 0 | |
| 4.78.0 | 1 / 0 | |
| 4.77.0 | 1 / 0 | |
| 4.76.0 | 1 / 0 | |
| 4.75.0 | 1 / 0 | |
| 4.74.1 | 1 / 0 | |
| 4.74.0 | 1 / 0 | |
| 4.73.0 | 1 / 0 | |
| 4.72.0 | 1 / 0 | |
| 4.71.1 | 1 / 0 | |
| 4.71.0 | 1 / 0 | |
| 4.70.0 | 1 / 0 | |
| 4.69.0 | 1 / 0 | |
| 4.68.0 | 1 / 0 | |
| 4.67.0 | 1 / 0 | |
| 4.66.0 | 1 / 0 | |
| 4.65.0 | 1 / 0 | |
| 4.64.0 | 1 / 0 | |
| 4.63.0 | 1 / 0 | |
| 4.62.1 | 1 / 0 | |
| 4.62.0 | 1 / 0 | |
| 4.61.0 | 1 / 0 |
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.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 (nsbarsukov) than the most recent previously approved version (vladimir.potekhin) on 2026-05-25, but nsbarsukov 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.
v5.7.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 (vladimir.potekhin) than the most recent previously approved version (nsbarsukov) on 2026-05-18, but vladimir.potekhin 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.
v5.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.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 (splincode) than the most recent previously approved version (nsbarsukov) on 2026-05-04, but splincode 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.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.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 (nsbarsukov) than the most recent previously approved version (vladimir.potekhin) on 2026-05-25, but nsbarsukov 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.
v4.83.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 (vladimir.potekhin) than the most recent previously approved version (nsbarsukov) on 2026-05-18, but vladimir.potekhin 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.
v4.82.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 (vladimir.potekhin) than the most recent previously approved version (nsbarsukov) on 2026-05-12, but vladimir.potekhin 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.
v4.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.1
14 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.
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.
v4.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.78.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.