@cleartrip/ct-design-components No license 27 versions

@cleartrip/ct-design-components

npm

27

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

rahulct_comsupragya.chauhannareshkapse_ctsaranshdawract_devopssidhantrajanhello_world_aryaritesh.kumarjenamohitjaincleartripashwin.ctashokmpatelamansaxena1prateek.oraonashwin-ui-ctshashi-kumar

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@cleartrip/ct-design-list	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
dependencies	unvetted-dep:@cleartrip/ct-design-carousel	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
dependencies	unvetted-dep:@cleartrip/ct-design-id-container	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
dependencies	unvetted-dep:@cleartrip/ct-design-lottie-player	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
dependencies	unvetted-dep:@cleartrip/ct-design-scroll-container	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
dependencies	unvetted-dep:@cleartrip/ct-design-sticky-container	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
dependencies	unvetted-dep:@cleartrip/ct-design-intersection-observer	AI (dependencies): First-party sibling package in same org/monorepo release.	ai	2026/07/13
phantom-deps	phantom-dep:@cleartrip/ct-design-animate	AI (phantom-deps): Same-org monorepo dependency, common heuristic false positive.	ai	2026/07/13

Versions (showing 27 of 27)

Version	Deps	Published
5.14.0	60 / 0	2026-07-13
3.20.0	80 / 0	2025-01-10
3.19.0	80 / 0	2024-12-27
3.18.0	79 / 0	2024-12-23
3.17.2	79 / 0	2024-11-26
3.17.1	79 / 0	2024-10-28
3.17.0	79 / 0	2024-10-24
3.16.1	79 / 0	2024-10-16
3.16.0	79 / 0	2024-10-15
3.15.0	79 / 0	2024-10-03
3.14.0	76 / 0	2024-09-09
3.13.0	76 / 0	2024-08-08
3.12.0	76 / 0	2024-08-06
3.11.0	76 / 0	2024-08-05
3.10.0	76 / 0	2024-07-30
3.9.0	76 / 0	2024-07-24
3.8.0	75 / 0	2024-07-23
3.7.0	75 / 0	2024-06-27
3.6.0	75 / 0	2024-06-25
3.5.0	75 / 0	2024-06-25
3.4.0	72 / 0	2024-06-20
3.3.0	72 / 0	2024-06-20
3.2.1	72 / 0	2024-06-10
3.2.0	72 / 0	2024-06-10
3.1.1	72 / 0	2024-06-04
3.1.0	72 / 0	2024-06-03
3.0.0	72 / 0	2024-05-30

v5.14.0

2 findings

LOW No provenance attestation provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

v3.18.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → saranshdawra (on 2024-12-23, known maintainer) provenance

This version was published by a different npm account (saranshdawra) than the most recent previously approved version (gkanishk1) on 2024-12-23, but saranshdawra 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.17.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → saranshdawra (on 2024-11-26, known maintainer) provenance

This version was published by a different npm account (saranshdawra) than the most recent previously approved version (gkanishk1) on 2024-11-26, but saranshdawra 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.17.1

1 finding

LOW No provenance attestation provenance

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

v3.17.0

1 finding

LOW No provenance attestation provenance

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

v3.16.1

1 finding

LOW No provenance attestation provenance

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

v3.16.0

1 finding

LOW No provenance attestation provenance

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

v3.15.0

1 finding

LOW No provenance attestation provenance

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

v3.14.0

1 finding

LOW No provenance attestation provenance

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

v3.13.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → ashutoshclearip (on 2024-08-08, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-08-08, but ashutoshclearip 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.12.0

1 finding

LOW No provenance attestation provenance

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

v3.11.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → bansalraghav19 (on 2024-08-05, known maintainer) provenance

This version was published by a different npm account (bansalraghav19) than the most recent previously approved version (gkanishk1) on 2024-08-05, but bansalraghav19 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.10.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ashutoshclearip → gkanishk1 (on 2024-07-30, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-07-30, but gkanishk1 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.9.0

1 finding

LOW No provenance attestation provenance

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

v3.8.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → ashutoshclearip (on 2024-07-23, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-07-23, but ashutoshclearip 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.7.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → ashutoshclearip (on 2024-06-27, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-06-27, but ashutoshclearip 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.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: ashutoshclearip → gkanishk1 (on 2024-06-25, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-06-25, but gkanishk1 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.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → ashutoshclearip (on 2024-06-25, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-06-25, but ashutoshclearip 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.4.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: bansalraghav19 → gkanishk1 (on 2024-06-20, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (bansalraghav19) on 2024-06-20, but gkanishk1 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.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → bansalraghav19 (on 2024-06-20, known maintainer) provenance

This version was published by a different npm account (bansalraghav19) than the most recent previously approved version (gkanishk1) on 2024-06-20, but bansalraghav19 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.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sidhantrajan → gkanishk1 (on 2024-06-10, known maintainer) provenance

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

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gkanishk1 → sidhantrajan (on 2024-06-04, known maintainer) provenance

This version was published by a different npm account (sidhantrajan) than the most recent previously approved version (gkanishk1) on 2024-06-04, 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.1.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.

v3.0.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.