@itentialopensource/adapter-cisco_tetration
This adapter integrates with system: sample.
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 preinstall pattern; runs node utils/setup.js, consistent across all versions of this package family. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — a static path join, not a truly dynamic require. Stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility/tooling operations; consistent with Itential adapter framework pattern across versions. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is declared in dependencies and referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts is declared in dependencies and used in setup utilities; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency referenced in config files; phantom-dep heuristic false positive. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.9.2 | 15 / 6 | |
| 0.9.0 | 15 / 6 |
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.
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.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.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.