@itentialopensource/adapter-opengear_lighthouse
This adapter integrates with system described as: lighthouseRestApi.
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 helper used across all Itential adapter packages; stable false positive for this package family. | ai | |
| provenance | no-provenance | AI (provenance): Itential publishes from GitLab CI without Sigstore attestation; consistent across all versions of this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in adapterBase.js for health checks and connectivity utilities; standard for this adapter framework. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is used in connectivity/troubleshoot scripts referenced in config; stable false positive for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Itential adapter framework uses node utils/setup.js preinstall consistently across all adapter packages; not malicious. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param used in test scripts via CLI config; stable false positive for this adapter package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in setup/migration utilities; referenced in config files as expected. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in adapterBase.js is a stable pattern for loading adapter components in the Itential framework. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 15 / 6 | |
| 1.0.2 | 15 / 6 | |
| 1.0.1 | 15 / 6 | |
| 1.0.0 | 15 / 6 | |
| 0.7.4 | 15 / 6 | |
| 0.7.3 | 15 / 6 | |
| 0.7.2 | 15 / 6 | |
| 0.7.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.
v0.7.4
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.7.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.
v0.7.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.7.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.