@itentialopensource/adapter-redis_cloud
This adapter integrates with system described as: redisCloud.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:mocha-param | AI (dependencies): mocha-param is a test/dev dependency used across all Itential adapter versions; not a runtime risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves local adapterBase.js via path.join(__dirname,...); not arbitrary module loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for standard adapter infrastructure; stable pattern across Itential adapters. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter preinstall pattern; runs local setup.js, consistent across all adapter versions. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): Referenced in config files per phantom-dep finding; stable false positive for this adapter pattern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 0.7.0 | 15 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
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.7.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.