← Home

@itentialopensource/adapter-opsramp

This adapter integrates with system described as: resourceManagement.

6
Versions
Apache-2.0
License
Yes
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

jared.obrienjohnpolanskyzack.strulovitchitential-ciandyknaebelishitaprakash

Keywords

ItentialItential PlatformAutomationIntegrationAdapteropsrampPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:mocha-param AI (dependencies): mocha-param is a test utility dependency; not a runtime risk for this adapter package. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require resolves adapterBase.js via path.join(__dirname,...) — not user-controlled; stable adapter framework pattern. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for adapter framework operations; consistent with Itential adapter architecture. ai
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter pattern; runs utils/setup.js for git hooks setup, consistent across all adapter versions. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in utility scripts (setup/migration), not main adapter code; stable false positive for this package. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test runner plugin referenced in test config, not directly imported; stable false positive. 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 module. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.3 15 / 6
1.0.1 15 / 6
0.6.3 15 / 6
0.6.0 15 / 6
0.4.1 15 / 6
0.4.0 15 / 6

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.3

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.6.0

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.1

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.0

2 findings
HIGH Package has 'preinstall' script install-scripts

Script: node utils/setup.js

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.