@itentialopensource/adapter-nokia_netact
This adapter integrates with system described as: Nokia Netact.
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 utility used in mocha test scripts; not a runtime security concern for this adapter package. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in config/connectivity checks, not directly imported in main code. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in utility scripts referenced in package.json scripts, not main module imports. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency referenced in test config files, not directly imported in source. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves known local paths (adapterBase.js etc.); stable adapter framework pattern. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync/spawnSync used in adapter base for legitimate system operations; consistent with Itential adapter framework. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; consistent across all versions of this adapter family. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 0.6.3 | 15 / 6 | |
| 0.6.1 | 15 / 6 | |
| 0.6.0 | 15 / 6 | |
| 0.5.1 | 15 / 6 | |
| 0.5.0 | 15 / 6 | |
| 0.4.1 | 15 / 6 | |
| 0.4.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.
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.
v0.6.3
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.
v0.6.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.5.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.
v0.5.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.4.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.
v0.4.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.