@cleartrip/ct-design-bottomsheet
Bottomsheet component
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@cleartrip/ct-design-hooks | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo peer/transitive usage. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-conditional-wrap | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic unreliable for monorepo peer/transitive usage. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Referenced in config files (e.g. babel/rollup emotion plugin config); not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Referenced in config files; stable false positive for this emotion-based component package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 15 / 4 | |
| 5.1.0 | 15 / 4 | |
| 5.0.0 | 15 / 4 | |
| 1.17.0 | 8 / 4 |
v5.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.