← Home

@cleartrip/ct-design-animate

npm

HOC component that will render animation to children

3
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:@emotion/react AI (phantom-deps): Referenced in build config (e.g. rollup/babel plugin config), not a direct import; stable false positive for this package. ai
phantom-deps phantom-dep:@emotion/styled AI (phantom-deps): Same as @emotion/react — config-level reference, not a direct import. ai
phantom-deps phantom-dep:@cleartrip/ct-design-theme AI (phantom-deps): Same-org design system dep; likely re-exported or used indirectly via style-manager. ai

Versions (showing 3 of 3)

Version Deps Published
5.1.0 6 / 2
5.0.0 6 / 2
1.13.0 0 / 2

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.

v1.13.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.