← Home

@syncfusion/ej2-react-pivotview

23
Versions
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

syncfusionorgessentialjs2syncfusion-javascript

Keywords

reactreactjsreact-pivotview

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): syncfusion-javascript is the org's current npm account with 230 approved packages; transition from essentialjs2 is a known org-level change. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects the account transition, not abandonment; syncfusion-javascript is actively publishing the full ej2 suite. ai
dependencies unvetted-dep:@syncfusion/ej2-pivotview AI (dependencies): Same-org Syncfusion dependency; standard React wrapper pattern, stable across versions. ai
phantom-deps phantom-dep:@syncfusion/ej2-base AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on re-exported packages from the Syncfusion suite. ai
provenance no-provenance AI (provenance): Syncfusion does not publish with Sigstore provenance; stable pattern across all their packages. ai

Versions (showing 23 of 23)

Version Deps Published
34.1.32 3 / 0
34.1.31 3 / 0
34.1.30 3 / 0
34.1.29 3 / 0
33.2.6 3 / 0
33.2.4 3 / 0
33.2.3 3 / 0
33.1.49 3 / 0
33.1.47 3 / 0
33.1.44 3 / 0
32.2.9 3 / 0
32.2.4 3 / 0
32.2.3 3 / 0
32.1.25 3 / 0
32.1.24 3 / 0
32.1.22 3 / 0
32.1.21 3 / 0
32.1.20 3 / 0
32.1.19 3 / 0
31.2.18 3 / 0
31.2.16 3 / 0
31.2.12 3 / 0
31.2.5 3 / 0

v34.1.32

1 finding
INFO No provenance attestation provenance

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

v34.1.31

1 finding
INFO No provenance attestation provenance

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

v34.1.30

1 finding
INFO No provenance attestation provenance

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

v34.1.29

1 finding
INFO No provenance attestation provenance

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

v33.2.6

1 finding
INFO No provenance attestation provenance

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