← Home

@cleartrip/ct-design-use-prop-state

npm
6
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

supragya.chauhannareshkapse_ctsaranshdawract_devopssidhantrajanhello_world_aryaritesh.kumarjenamohitjaincleartripashwin.ctashokmpatelamansaxena1ashwin-ui-ctshashi-kumar

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal corporate design-system package; missing metadata is consistent across the entire @cleartrip/* namespace. ai
npm-metadata no-description AI (npm-metadata): Stable pattern across @cleartrip/* scoped packages; not indicative of malice. ai
provenance no-provenance AI (provenance): Internal package; provenance not expected for this publisher's workflow. ai

Versions (showing 6 of 6)

Version Deps Published
5.6.0 1 / 0
5.5.0 1 / 0
5.2.0 1 / 0
5.1.0 1 / 0
5.0.0 1 / 0
3.20.0 1 / 0

v5.6.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.

v5.5.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.

v5.2.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.

v5.1.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.

v5.0.0

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: saranshdawra → sidhantrajan (on 2026-06-02, known maintainer) provenance

This version was published by a different npm account (sidhantrajan) than the most recent previously approved version (saranshdawra) on 2026-06-02, but sidhantrajan 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.

v3.20.0

1 finding
LOW No provenance attestation provenance

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