primeng
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/primeng-motion.mjs | AI (source-diff): Standard Angular FESM2022 build output; long lines are normal for this format. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump adds new modules; expected for Angular component library. | ai | |
| dependencies | unvetted-dep:@primeuix/motion | AI (dependencies): First-party PrimeTek package under the @primeuix namespace, same as other already-accepted primeng deps. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a well-known Angular/TypeScript runtime helper; phantom-dep false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 21.1.9 | 5 / 0 | |
| 21.1.8 | 5 / 0 | |
| 21.1.7 | 5 / 0 | |
| 21.1.6 | 5 / 0 | |
| 21.1.5 | 5 / 0 | |
| 21.1.4 | 5 / 0 | |
| 21.1.3 | 5 / 0 | |
| 21.1.2 | 5 / 0 | |
| 21.1.1 | 5 / 0 | |
| 21.1.0 | 5 / 0 | |
| 21.0.4 | 5 / 0 | |
| 21.0.3 | 5 / 0 | |
| 21.0.2 | 5 / 0 | |
| 21.0.1 | 5 / 0 | |
| 21.0.0 | 5 / 0 | |
| 20.4.0 | 4 / 0 | |
| 19.1.4 | 3 / 0 |
v21.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.8
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.
v21.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v21.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v21.1.0
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
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 (mert.sincan) than the most recent previously approved version (mehmetcetin) on 2025-12-15, but mert.sincan 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 (cagatay.civici) than the most recent previously approved version (mehmetcetin) on 2025-12-04, but cagatay.civici 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 (cagatay.civici) than the most recent previously approved version (mehmetcetin) on 2025-12-04, but cagatay.civici 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.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.