@cleartrip/ct-design-badge ISC 37 versions

@cleartrip/ct-design-badge

npm

Badge component

37

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

rahulct_comsupragya.chauhannareshkapse_ctsaranshdawract_devopssidhantrajanhello_world_aryaritesh.kumarjenamohitjaincleartripashwin.ctashokmpatelamansaxena1prateek.oraonashwin-ui-ctshashi-kumar

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-level team rotation at Cleartrip; consistent with internal team changes across design system packages.	ai	2026/06/03
maintainer-change	maintainer-removed	AI (maintainer-change): Paired with maintainer-added; reflects org team rotation, not a hostile takeover.	ai	2026/06/03
publish-pattern	new-deps-added	AI (publish-pattern): New deps are internal @cleartrip/ct-design-* packages at matching v5.0.0; coordinated major version bump.	ai	2026/06/03
phantom-deps	phantom-dep:@cleartrip/ct-design-container	AI (phantom-deps): Same-org design-system dep; phantom-dep heuristic is a stable false positive for this package family.	ai	2026/04/28

Versions (showing 37 of 37)

Version	Deps	Published
5.15.0	5 / 2	2026-07-20
5.14.0	5 / 2	2026-07-13
5.13.0	5 / 2	2026-07-07
5.12.0	5 / 2	2026-06-25
5.11.0	5 / 2	2026-06-18
5.10.0	5 / 2	2026-06-16
5.9.0	5 / 2	2026-06-16
5.7.0	5 / 2	2026-06-15
5.6.0	5 / 2	2026-06-02
5.5.0	5 / 2	2026-06-02
5.2.0	5 / 2	2026-06-02
5.1.0	5 / 2	2026-06-02
5.0.0	5 / 2	2026-06-02
2.22.0	3 / 2	2026-06-09
2.20.0	3 / 2	2025-01-10
2.19.0	3 / 2	2024-12-27
2.18.0	3 / 2	2024-12-23
2.17.0	3 / 2	2024-10-24
2.16.1	3 / 2	2024-10-16
2.16.0	3 / 2	2024-10-15
2.15.0	3 / 2	2024-10-03
2.14.0	3 / 2	2024-09-09
2.13.0	3 / 2	2024-08-08
2.12.0	3 / 2	2024-08-06
2.11.0	3 / 2	2024-08-05
2.10.0	3 / 2	2024-07-30
2.9.0	3 / 2	2024-07-24
2.8.0	3 / 2	2024-07-23
2.7.0	3 / 2	2024-06-27
2.6.0	3 / 2	2024-06-25
2.5.0	3 / 2	2024-06-25
2.4.0	3 / 2	2024-06-20
2.3.0	3 / 2	2024-06-20
2.2.0	3 / 2	2024-06-10
2.1.1	3 / 2	2024-06-04
2.1.0	3 / 2	2024-06-03
2.0.0	3 / 2	2024-05-30

v5.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.18.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: gkanishk1 → saranshdawra (on 2024-12-23, known maintainer) provenance

This version was published by a different npm account (saranshdawra) than the most recent previously approved version (gkanishk1) on 2024-12-23, but saranshdawra 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.

v2.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.14.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: ashutoshclearip → gkanishk1 (on 2024-09-09, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-09-09, but gkanishk1 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.

v2.13.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: gkanishk1 → ashutoshclearip (on 2024-08-08, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-08-08, but ashutoshclearip 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.

v2.12.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: bansalraghav19 → gkanishk1 (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (bansalraghav19) on 2024-08-06, but gkanishk1 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.

v2.11.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: gkanishk1 → bansalraghav19 (on 2024-08-05, known maintainer) provenance

This version was published by a different npm account (bansalraghav19) than the most recent previously approved version (gkanishk1) on 2024-08-05, but bansalraghav19 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.

v2.10.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: ashutoshclearip → gkanishk1 (on 2024-07-30, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-07-30, but gkanishk1 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.

v2.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.7.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: gkanishk1 → ashutoshclearip (on 2024-06-27, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-06-27, but ashutoshclearip 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.

v2.6.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: ashutoshclearip → gkanishk1 (on 2024-06-25, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (ashutoshclearip) on 2024-06-25, but gkanishk1 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.

v2.5.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: gkanishk1 → ashutoshclearip (on 2024-06-25, known maintainer) provenance

This version was published by a different npm account (ashutoshclearip) than the most recent previously approved version (gkanishk1) on 2024-06-25, but ashutoshclearip 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.

v2.4.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: bansalraghav19 → gkanishk1 (on 2024-06-20, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (bansalraghav19) on 2024-06-20, but gkanishk1 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.

v2.3.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: gkanishk1 → bansalraghav19 (on 2024-06-20, known maintainer) provenance

This version was published by a different npm account (bansalraghav19) than the most recent previously approved version (gkanishk1) on 2024-06-20, but bansalraghav19 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.

v2.2.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: sidhantrajan → gkanishk1 (on 2024-06-10, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (sidhantrajan) on 2024-06-10, but gkanishk1 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.

v2.1.1

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: gkanishk1 → sidhantrajan (on 2024-06-04, known maintainer) provenance

This version was published by a different npm account (sidhantrajan) than the most recent previously approved version (gkanishk1) on 2024-06-04, 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.

v2.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: omprakash07 → gkanishk1 (on 2024-06-03, known maintainer) provenance

This version was published by a different npm account (gkanishk1) than the most recent previously approved version (omprakash07) on 2024-06-03, but gkanishk1 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.

v2.0.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.