@pega/lists-react
Repeating view structures such as Table, Gallery(Repeating layouts), Kanban etc.
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-ui-list-data-apis | AI (dependencies): npm: alias for @pega/lists-core-utils — first-party Pegasystems package, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@pega/cosmos-react-core | AI (dependencies): First-party @pega/* dependency; consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:pega-repeating-structures-core | AI (dependencies): npm: alias for @pega/lists-core — first-party Pegasystems package, stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): TypeScript type-only package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/lodash.get | AI (phantom-deps): TypeScript type-only package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): TypeScript type-only package; not directly imported at runtime by convention. | ai | |
| phantom-deps | phantom-dep:@types/uuid | AI (phantom-deps): TypeScript type-only package; not directly imported at runtime by convention. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.21.4 | 19 / 12 | |
| 8.20.0 | 19 / 12 | |
| 8.19.0 | 19 / 12 | |
| 8.18.2 | 19 / 12 | |
| 8.17.0 | 19 / 12 | |
| 8.16.0 | 19 / 12 | |
| 8.9.2 | 19 / 12 | |
| 8.8.1 | 19 / 12 |
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.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.17.0
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.
v8.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.