@itentialopensource/adapter-spirent_testcenter
This adapter integrates with system described as: Spirent test center.
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; stable across all versions of this package family. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Path-based require for adapterBase.js; not arbitrary user input. Stable pattern in Itential adapters. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync/spawnSync used for network adapter operations; expected in this adapter framework. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this adapter package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this adapter package. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): Referenced in config files per analyzer note; stable false positive for this adapter package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.6.1 | 15 / 6 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.6.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.