@itentialopensource/adapter-beyond_trust
This adapter integrates with system described as: beyondtrustPrivilegedRemoteAccessConfigurationApis.
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/dev dependency used in the adapter framework; stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires on path.join(__dirname, 'adapterBase.js') — a static path, not truly dynamic; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used for adapter tooling utilities; consistent pattern across Itential adapter ecosystem. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): Standard Itential adapter preinstall pattern; runs node utils/setup.js, consistent across all adapter versions. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): prompts used in interactive utility scripts, not main adapter code; stable false positive. | ai | |
| phantom-deps | phantom-dep:mocha-param | AI (phantom-deps): mocha-param referenced in test config files; phantom-dep heuristic fires on indirect usage. | ai | |
| phantom-deps | phantom-dep:ping | AI (phantom-deps): ping is a declared runtime dep used in config/connectivity scripts, not directly imported in main code. | ai |
Versions (showing 7 of 7)
| 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.2 | 15 / 6 | |
| 0.7.0 | 15 / 6 | |
| 0.5.1 | 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.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.
v0.5.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.