← Home

@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

31
Versions
SEE LICENSE IN LICENSE
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

baipcandrewlewis2duddrcricmarsssowersbybob-difronzofeenr-pegacpmotionpega-cosmosghosa4sharv12tumms2021389vrspegapatilvishalnikhilparmar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/lodash-es AI (phantom-deps): TypeScript types package for lodash-es; conventionally loaded alongside the runtime dep. ai
maintainer-change maintainer-removed AI (maintainer-change): Active Pega org publisher with strong approval track record; removal without new addition indicates internal cleanup, not takeover. ai
publish-pattern rapid-publish AI (publish-pattern): Pega monorepo CI regularly publishes many packages in quick succession; pattern is stable across their releases. ai
publish-pattern new-deps-added AI (publish-pattern): lodash-es is an established package replacing lodash.get; not a suspicious new dependency. ai
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 31 of 31)

Version Deps Published
9.10.1 6 / 1
9.8.0 6 / 1
9.5.4 6 / 1
9.5.2 6 / 1
9.1.1 6 / 1
9.0.0 6 / 1
8.21.21 6 / 1
8.21.19 6 / 1
8.21.17 6 / 1
8.21.15 6 / 1
8.21.12 6 / 1
8.21.7 6 / 1
8.21.4 6 / 1
8.20.0 6 / 1
8.19.0 6 / 1
8.18.2 6 / 1
8.18.1 6 / 1
8.17.2 6 / 1
8.17.1 6 / 1
8.17.0 6 / 1
8.16.1 6 / 1
8.16.0 6 / 1
8.15.0 6 / 1
8.14.0 6 / 1
8.13.1 6 / 1
8.13.0 6 / 1
8.12.1 6 / 1
8.11.0 6 / 1
8.9.4 6 / 1
8.9.2 6 / 1
8.9.0 6 / 1

v9.10.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.8.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v9.5.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.21

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.19

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.17

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.15

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.21.12

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.11.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v8.9.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.