← Home

@cleartrip/ct-design-horizontal-scroll

npm

HorizontalScroll Component

4
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
phantom-deps phantom-dep:@cleartrip/ct-design-icons AI (phantom-deps): Same-org design system dep; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@cleartrip/ct-design-theme AI (phantom-deps): Same-org design system dep; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@cleartrip/ct-design-tooltip AI (phantom-deps): Same-org design system dep; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@cleartrip/ct-design-common-utils AI (phantom-deps): Same-org design system dep; phantom-dep heuristic unreliable for monorepo packages. ai
dependencies unvetted-dep:@cleartrip/ct-design-theme AI (dependencies): Internal Cleartrip design-system sibling package; expected dependency pattern across all versions. ai
dependencies unvetted-dep:@cleartrip/ct-design-common-utils AI (dependencies): Internal Cleartrip design-system sibling package; expected dependency pattern across all versions. ai
dependencies unvetted-dep:@cleartrip/ct-design-icons AI (dependencies): Internal Cleartrip design-system sibling package; expected dependency pattern across all versions. ai

Versions (showing 4 of 4)

Version Deps Published
5.5.0 9 / 1
5.1.0 9 / 1
5.0.0 9 / 1
3.20.0 4 / 2

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

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

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