@itentialopensource/adapter-zabbix
zabbix adapter
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework standard setup script; consistent across all adapter-* packages in this org. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Adapter framework loads components via path.join(__dirname, ...) — deterministic, not user-controlled. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): adapterBase.js uses execSync/spawnSync for adapter utility operations; standard in Itential adapter base. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in connectivity/healthcheck utility scripts referenced in package.json scripts block. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive setup/migration utilities, not main module imports. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test helper referenced in test config files, not directly imported in source. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 0.9.2 | 15 / 6 | |
| 0.9.1 | 15 / 6 | |
| 0.9.0 | 15 / 6 |
v1.0.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.
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.9.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.
v0.9.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.9.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.