@verisoft/ui-govcz
A comprehensive Angular UI component library that provides components specifically designed to comply with Czech Government Design System (gov.cz) standards. This library offers a complete set of form controls, navigation components, and layout elements t
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:fesm2022/verisoft-ui-govcz.mjs | AI (source-diff): Standard Angular FESM2022 bundle; long lines are normal compiler output, not obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Angular library bundle growth tracks component additions; not indicative of injected payload. | ai | |
| phantom-deps | phantom-dep:@gov-design-system-ce/styles | AI (phantom-deps): CSS/style package referenced via config files, not JS imports; phantom-dep false positive stable for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly declared in dependencies; phantom-dep fires as a false positive here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 21.0.13 | 5 / 0 | |
| 21.0.12 | 5 / 0 | |
| 21.0.11 | 6 / 0 | |
| 21.0.10 | 6 / 0 | |
| 21.0.9 | 6 / 0 | |
| 21.0.8 | 6 / 0 | |
| 21.0.7 | 6 / 0 | |
| 21.0.6 | 6 / 0 | |
| 21.0.5 | 6 / 0 | |
| 21.0.4 | 6 / 0 | |
| 21.0.3 | 6 / 0 | |
| 21.0.2 | 6 / 0 | |
| 21.0.1 | 6 / 0 | |
| 21.0.0 | 6 / 0 | |
| 20.2.0 | 6 / 0 | |
| 20.1.3 | 6 / 0 | |
| 20.1.2 | 6 / 0 | |
| 20.1.1 | 5 / 0 | |
| 20.1.0 | 5 / 0 |
v21.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.0.1
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 (martin.holava) than the most recent previously approved version (hung.nguyen02) on 2026-01-02, but martin.holava 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.0.0
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 (martin.holava) than the most recent previously approved version (hung.nguyen02) on 2026-01-02, but martin.holava 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.
v20.2.0
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.
v20.1.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.
v20.1.2
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.
v20.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.