@itentialopensource/adapter-glds_customerexperiencegateway
This adapter integrates with system described as: GLDS Customer Experience Gateway.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter pattern; setup.js is a documented utility script consistent across all adapter versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Requires adapterBase.js by constructed path using __dirname, not user-controlled input; stable pattern across Itential adapters. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility operations (healthcheck, connectivity); consistent with Itential adapter framework. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared dependency used in config/utility scripts; phantom-dep heuristic false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts is a declared dependency used in utility scripts; phantom-dep heuristic false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency referenced in config; phantom-dep heuristic false positive for this adapter pattern. | ai |
v1.0.1
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
2 findingsScript: node utils/setup.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.