@verisoft/ui-primeng
A comprehensive Angular UI component library built on top of PrimeNG that provides enterprise-grade components with modern design and extensive functionality. This library combines the power of PrimeNG with Verisoft's design patterns to deliver consistent
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-primeng.mjs | AI (source-diff): Standard Angular FESM2022 compiled bundle; long lines are normal minified Angular output, not obfuscation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known Angular/TypeScript implicit runtime dep; phantom detection is a stable false positive here. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 21.0.13 | 2 / 0 | |
| 21.0.12 | 2 / 0 | |
| 21.0.11 | 2 / 0 | |
| 21.0.10 | 2 / 0 | |
| 21.0.9 | 2 / 0 | |
| 21.0.8 | 2 / 0 | |
| 21.0.7 | 2 / 0 | |
| 21.0.6 | 2 / 0 | |
| 21.0.5 | 2 / 0 | |
| 21.0.4 | 2 / 0 | |
| 21.0.3 | 2 / 0 | |
| 21.0.2 | 2 / 0 | |
| 21.0.1 | 2 / 0 | |
| 21.0.0 | 2 / 0 | |
| 20.2.0 | 2 / 0 | |
| 20.1.3 | 2 / 0 | |
| 20.1.2 | 2 / 0 | |
| 20.1.1 | 1 / 0 | |
| 20.1.0 | 1 / 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
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 (martin.holava) than the most recent previously approved version (hung.nguyen02) on 2026-01-27, 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.4
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 (martin.holava) than the most recent previously approved version (hung.nguyen02) on 2026-01-23, 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.3
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 (martin.holava) than the most recent previously approved version (hung.nguyen02) on 2026-01-09, 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.2
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 (martin.holava) than the most recent previously approved version (hung.nguyen02) on 2026-01-05, 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.1
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 (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
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 (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.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.