@cleartrip/ct-platform-wallet-balance-history
Wallet balance history Component
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cleartrip/ct-design-theme | AI (dependencies): Internal @cleartrip org dependency; consistent with this package's monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-button | AI (dependencies): Internal @cleartrip org dependency; consistent with this package's monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-divider | AI (dependencies): Internal @cleartrip org dependency; consistent with this package's monorepo pattern across all versions. | ai | |
| dependencies | unvetted-dep:@cleartrip/ct-design-container | AI (dependencies): Internal @cleartrip org dependency; consistent with this package's monorepo pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-platform-shimmer | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in bundled output. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-button | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in bundled output. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-platform-text-badge | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in bundled output. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-divider | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in bundled output. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-platform-utils | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in bundled output. | ai | |
| phantom-deps | phantom-dep:@cleartrip/ct-design-container | AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in bundled output. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.3.31 | 9 / 0 | |
| 4.3.30 | 9 / 0 | |
| 4.3.29 | 9 / 0 | |
| 4.3.28 | 9 / 0 | |
| 4.3.27 | 9 / 0 | |
| 4.3.26 | 9 / 0 | |
| 4.3.25 | 9 / 0 | |
| 4.3.24 | 9 / 0 | |
| 4.3.23 | 9 / 0 | |
| 4.3.22 | 9 / 0 | |
| 4.3.21 | 9 / 0 | |
| 4.3.20 | 9 / 0 | |
| 4.3.19 | 9 / 0 | |
| 4.3.10 | 9 / 0 | |
| 4.3.9 | 9 / 0 | |
| 4.3.8 | 9 / 0 | |
| 4.3.7 | 9 / 0 | |
| 4.3.6 | 9 / 0 | |
| 4.3.5 | 9 / 0 | |
| 4.3.4 | 9 / 0 | |
| 4.3.3 | 9 / 0 | |
| 4.3.2 | 9 / 0 | |
| 4.3.0 | 9 / 0 | |
| 4.1.1 | 9 / 0 | |
| 4.1.0 | 9 / 0 | |
| 4.0.0 | 9 / 0 |
v4.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
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 (ritesh.kumarjena) than the most recent previously approved version (ashokmpatel) on 2025-04-16, but ritesh.kumarjena 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.
v4.3.8
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 (ritesh.kumarjena) than the most recent previously approved version (ashokmpatel) on 2025-04-16, but ritesh.kumarjena 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.
v4.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
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 (ashokmpatel) than the most recent previously approved version (ritesh.kumarjena) on 2025-04-11, but ashokmpatel 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.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.