@itentialopensource/adapter-whatsup_gold
This adapter integrates with system described as: WhatsUp Gold
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 uses preinstall for git hooks/setup; consistent across all adapter versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is a structural pattern of the Itential adapter base framework, not arbitrary code loading. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter utility scripts (migration, healthcheck); consistent with framework design. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared dependency used in config/connectivity scripts, not directly imported in main code. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in utility/setup scripts referenced by npm scripts, not main adapter code. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param is a test dependency used via mocha config, not directly imported. | ai |
v1.0.3
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.