@itentialopensource/adapter-nokia_nsp_network_management
This adapter integrates with system described as: NSP Network Infrastructure Management
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): Itential adapter framework uses node utils/setup.js preinstall consistently across all adapter packages; not malicious. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in adapter.js loads adapterBase.js via path.join — standard Itential adapter pattern, not arbitrary module loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for diagnostics/healthcheck utilities; consistent with Itential adapter-utils framework. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dependency used in connectivity/healthcheck scripts, not directly imported in main module. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in utility scripts (setup/migration), not main adapter code; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; phantom-dep false positive for this package. | ai |
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.
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.