@itentialopensource/adapter-firemon_securitymanager
This adapter integrates with system described as: securityManagerApi.
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): Publisher has 290 approved packages and no material changes vs prior version; dormancy reflects maintenance cadence, not takeover. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is part of the Itential adapter base framework pattern, not malicious. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require with __dirname is a safe path-relative load pattern used throughout the Itential adapter framework. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter framework setup script; consistent across all versions of this package family. | 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.