@cleartrip/ct-design-counter
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): Active internal team rotation within Cleartrip org; consistent with large design-system monorepo maintenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with maintainer-added; reflects team changes, not a hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @cleartrip/[email protected] — same org, same major version bump, not a third-party package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Cleartrip internal design system component; sparse metadata is consistent across all versions of this org's packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-wide pattern for Cleartrip design system packages; not a malware indicator here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 5 / 1 | |
| 5.5.0 | 5 / 1 | |
| 5.2.0 | 5 / 1 | |
| 5.1.0 | 5 / 1 | |
| 5.0.0 | 5 / 1 | |
| 3.20.0 | 4 / 1 |
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.