@cleartrip/ct-design-checkbox
Checkbox 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Cleartrip internal team rotation; new maintainers are part of the same org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Cleartrip internal team rotation; removals consistent with org restructuring. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by addition of ct-design-typography and ct-design-style-manager internal deps. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-tokens | AI (dependencies): First-party Cleartrip design-system dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-icons | AI (dependencies): First-party Cleartrip design-system dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-container | AI (dependencies): First-party Cleartrip design-system dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-theme | AI (dependencies): First-party Cleartrip design-system dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-types | AI (dependencies): First-party Cleartrip design-system dep; stable pattern across all versions of this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 6 / 0 | |
| 5.5.0 | 6 / 0 | |
| 5.2.0 | 6 / 0 | |
| 5.1.0 | 6 / 0 | |
| 5.0.0 | 6 / 0 | |
| 3.20.0 | 5 / 0 |
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.2.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.