← Home

@cleartrip/ct-design-coupon

npm
23
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

hello_world_aryaashutoshclearipbansalraghav19sidhantrajannavjot.s9meera.mendhesaranshdawragkanishk1khushahalsudo_harshvardhanritesh.kumarjenaomprakash07mohitjaincleartripnareshkapse_ctjay_prakash

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): New publisher has strong 467/0 track record; no behavioral change in diff. ai
maintainer-change maintainer-added AI (maintainer-change): Consistent with org-internal maintainer transition, no code changes. ai
bogus-package bogus-package AI (bogus-package): Internal design-system monorepo component; missing metadata is a consistent pattern across all @cleartrip/ct-design-* packages, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Stable pattern across all @cleartrip/ct-design-* packages; not indicative of malicious intent. ai

Versions (showing 23 of 23)

Version Deps Published
3.22.0 2 / 2
3.20.0 2 / 2
3.19.0 2 / 2
3.18.0 2 / 2
3.17.0 2 / 2
3.16.0 2 / 2
3.15.0 2 / 2
3.14.0 2 / 2
3.13.0 2 / 2
3.12.0 2 / 2
3.11.0 2 / 2
3.10.0 2 / 2
3.9.0 2 / 2
3.8.0 2 / 2
3.7.0 2 / 2
3.6.0 2 / 2
3.5.0 2 / 2
3.4.0 2 / 2
3.3.0 2 / 2
3.2.0 2 / 2
3.1.1 2 / 2
3.1.0 2 / 2
3.0.0 2 / 2

v3.19.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-27, known maintainer) provenance

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

v3.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.

v3.17.0

1 finding
LOW No provenance attestation provenance

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

v3.16.0

1 finding
LOW No provenance attestation provenance

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

v3.15.0

1 finding
LOW No provenance attestation provenance

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

v3.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.

v3.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.

v3.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.

v3.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.

v3.10.0

1 finding
LOW No provenance attestation provenance

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

v3.9.0

2 findings
HIGH Publisher changed: gkanishk1 → ashutoshclearip (on 2024-07-24) provenance

This version was published by a different npm account than previous versions on 2024-07-24. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.8.0

2 findings
HIGH Publisher changed: gkanishk1 → ashutoshclearip (on 2024-07-23) provenance

This version was published by a different npm account than previous versions on 2024-07-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.7.0

2 findings
HIGH Publisher changed: gkanishk1 → ashutoshclearip (on 2024-06-27) provenance

This version was published by a different npm account than previous versions on 2024-06-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.6.0

1 finding
LOW No provenance attestation provenance

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

v3.5.0

2 findings
HIGH Publisher changed: gkanishk1 → ashutoshclearip (on 2024-06-25) provenance

This version was published by a different npm account than previous versions on 2024-06-25. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.4.0

1 finding
LOW No provenance attestation provenance

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

v3.3.0

2 findings
HIGH Publisher changed: sidhantrajan → bansalraghav19 (on 2024-06-20) provenance

This version was published by a different npm account than previous versions on 2024-06-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.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.

v3.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: omprakash07 → 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 (omprakash07) 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.

v3.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.

v3.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.