@cleartrip/ct-design-segment
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 dep; phantom-dep heuristic fires on indirect/re-exported usage common in monorepo component packages. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-tokens | AI (phantom-deps): Same-org monorepo package; declared but indirectly used pattern is stable across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 8 / 1 | |
| 5.5.0 | 8 / 1 | |
| 5.1.0 | 8 / 1 | |
| 5.0.0 | 8 / 1 | |
| 3.20.0 | 3 / 1 |
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.5.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.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.