@cleartrip/ct-design-tooltip
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Large org-wide design system; maintainer rotation is expected across major version bumps. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same context as maintainer-added; org team rotation, not a takeover signal. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): Referenced in build config (Emotion babel plugin); not a direct import but a legitimate peer/build dep. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Same as @emotion/react — build config reference, not a phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-use-merge-refs | AI (phantom-deps): Same-org package; likely re-exported or used indirectly through another ct-design dep. | ai | |
| provenance | no-provenance | AI (provenance): Established Cleartrip design system package; no provenance is consistent across all versions. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 10 / 3 | |
| 5.5.0 | 10 / 3 | |
| 5.2.0 | 10 / 3 | |
| 5.1.0 | 10 / 3 | |
| 5.0.0 | 10 / 3 | |
| 3.20.0 | 9 / 0 |
v5.6.0
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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.2.0
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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.