@itentialopensource/adapter-nautobot_v2
This adapter integrates with system described as: Nautobot.
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; stable pattern across this adapter family. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility operations (healthcheck, connectivity, migration); stable framework pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads local JSON config files via __dirname; not arbitrary user input; stable adapter framework pattern. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter setup script pattern; consistent across all versions of this adapter family. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive setup/migration utilities; stable false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; stable false positive for this adapter pattern. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in adapter connectivity utilities referenced in config/scripts, not directly imported in main code. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.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.
v1.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.