@cleartrip/ct-design-accordion-group
AccordionGroup
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 design system org rotates team members across all packages; pattern is consistent with org-wide team changes. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org team rotation; removals mirror additions across the design system monorepo. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-style-manager | AI (phantom-deps): Same-org scoped dep used as a peer/indirect dep in a design system; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-icons | AI (phantom-deps): Same-org design system dep; phantom-dep heuristic fires on transitive/re-exported usage patterns common in monorepos. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-accordion-v2 | AI (phantom-deps): Same-org design system dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-theme | AI (phantom-deps): Same-org design system dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-typography | AI (phantom-deps): Same-org design system dep; stable false positive for this monorepo package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.6.0 | 7 / 1 | |
| 5.5.0 | 7 / 1 | |
| 5.2.0 | 7 / 1 | |
| 5.1.0 | 7 / 1 | |
| 5.0.0 | 7 / 1 | |
| 2.22.0 | 7 / 1 | |
| 2.20.0 | 7 / 1 |
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.