@pega/lists-core-utils
Data api for data operations like sort, filter, grouping etc. and query builder api's to build Data views api query
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:pega-repeating-structures-core | AI (dependencies): Alias to @pega/lists-core within the same org and version; stable pattern across releases. | ai | |
| provenance | no-provenance | AI (provenance): Pega publishes without Sigstore provenance consistently across all versions; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/lodash.get | AI (phantom-deps): @types packages are type-only and not directly imported at runtime; false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.21.4 | 6 / 1 | |
| 8.20.0 | 6 / 1 | |
| 8.18.2 | 6 / 1 | |
| 8.18.1 | 6 / 1 | |
| 8.17.2 | 6 / 1 | |
| 8.16.1 | 6 / 1 | |
| 8.16.0 | 6 / 1 |
v8.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.