@itentialopensource/adapter-nokia_nsp_nfm_p
This adapter integrates with system described as: nfm-p(SAMO).
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established Itential adapter with 35 versions; publisher has 290 approved packages — dormancy reflects product cadence, not takeover. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for standard adapter operations; stable pattern across Itential adapter framework. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads local sampleProperties.json via __dirname; not arbitrary module loading, stable pattern in this framework. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter pattern; preinstall runs setup.js for git hooks/config, consistent across all org adapters. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive CLI utilities; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in adapter connectivity utilities; phantom-dep heuristic false positive for this package. | ai |
v1.0.2
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.