@itentialopensource/adapter-netbox_v33
This adapter integrates with system described as: Netbox v3.3
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-only dependency pinned to 2.0.1; no runtime exposure for this adapter package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 290 approved packages and no material changes vs prior version; dormancy reflects release cadence, not takeover. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic requires resolve local JSON config files via __dirname; not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in adapter connectivity scripts referenced in config, not directly imported in main code. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework uses node utils/setup.js as a standard preinstall step across all adapter versions. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test utility referenced in test config files, not directly imported in main code. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts is used in adapter utility scripts, not directly imported in main code. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter connectivity/healthcheck tooling; stable pattern across Itential adapter framework. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 15 / 6 | |
| 3.0.2 | 15 / 6 | |
| 3.0.1 | 15 / 6 | |
| 3.0.0 | 15 / 6 |
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.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.
v3.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.