@icgio/clients-config
Centralized configuration management for ICG trading clients. Contains client trading configurations and protected secret files managed with git-secret.
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): safe_require wrapper with MODULE_NOT_FOUND guard; stable benign pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped config package; sparse README/keywords expected for private tooling. | ai |
Versions (showing 22 of 122)
| Version | Deps | Published |
|---|---|---|
| 1.0.153 | 1 / 3 | |
| 1.0.152 | 1 / 3 | |
| 1.0.149 | 1 / 3 | |
| 1.0.148 | 1 / 3 | |
| 1.0.146 | 1 / 3 | |
| 1.0.144 | 1 / 3 | |
| 1.0.143 | 1 / 3 | |
| 1.0.140 | 1 / 3 | |
| 1.0.139 | 1 / 3 | |
| 1.0.138 | 1 / 3 | |
| 1.0.137 | 1 / 3 | |
| 1.0.136 | 1 / 3 | |
| 1.0.135 | 1 / 3 | |
| 1.0.134 | 1 / 3 | |
| 1.0.133 | 1 / 3 | |
| 1.0.132 | 1 / 3 | |
| 1.0.131 | 1 / 3 | |
| 1.0.130 | 1 / 3 | |
| 1.0.129 | 1 / 3 | |
| 1.0.128 | 1 / 3 | |
| 1.0.127 | 1 / 3 | |
| 1.0.126 | 1 / 3 |
v1.0.153
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.152
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.