@cleartrip/ct-design-outside-click-handler
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Scoped internal-org package; maintainer handoff within Cleartrip, no behavior change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Internal org maintainer addition, consistent with prior approved content. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-theme | AI (phantom-deps): Same-org dep declared but not directly imported; consistent with design-system peer/theme pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established Cleartrip design system package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 5.15.0 | 2 / 1 | |
| 5.14.0 | 2 / 1 | |
| 5.13.0 | 2 / 1 | |
| 5.12.0 | 2 / 1 | |
| 5.11.0 | 2 / 1 | |
| 5.10.0 | 2 / 1 | |
| 5.9.0 | 2 / 1 | |
| 5.7.0 | 2 / 1 | |
| 5.6.0 | 2 / 1 | |
| 5.5.0 | 2 / 1 | |
| 5.2.0 | 2 / 1 | |
| 5.1.0 | 2 / 1 | |
| 5.0.0 | 2 / 1 | |
| 3.22.0 | 1 / 1 | |
| 3.20.0 | 1 / 1 | |
| 3.19.0 | 1 / 1 | |
| 3.18.0 | 1 / 1 | |
| 3.17.0 | 1 / 1 | |
| 3.16.0 | 1 / 1 | |
| 3.15.0 | 1 / 1 | |
| 3.14.0 | 1 / 1 | |
| 3.13.0 | 1 / 1 | |
| 3.12.0 | 1 / 1 | |
| 3.11.0 | 1 / 1 | |
| 3.10.0 | 1 / 1 | |
| 3.9.0 | 1 / 1 | |
| 3.8.0 | 1 / 1 | |
| 3.7.0 | 1 / 1 | |
| 3.6.0 | 1 / 1 | |
| 3.5.0 | 1 / 1 | |
| 3.4.0 | 1 / 1 | |
| 3.3.0 | 1 / 1 | |
| 3.2.0 | 1 / 1 | |
| 3.1.0 | 1 / 1 | |
| 3.0.0 | 1 / 1 |
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.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 (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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.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 (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[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 (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[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 (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[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 (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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsThis 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.