@itentialopensource/adapter-robustel
This adapter integrates with system described as: robustel.
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 setup script pattern; runs local node utils/setup.js, not remote code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Itential adapter framework uses path.join(__dirname, ...) dynamic require for local module loading; stable pattern across all versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): adapterBase.js uses execSync/spawnSync for adapter utility operations; consistent with Itential adapter framework design. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in adapter connectivity utilities referenced in config/scripts, not directly imported in main code. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts is used in adapter setup/migration utilities, not directly imported in main adapter code. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test utility referenced in test config files, not directly imported in main code. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 16 / 6 | |
| 1.0.1 | 16 / 6 | |
| 1.0.0 | 16 / 6 | |
| 0.7.0 | 16 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.