← Home

@itentialopensource/adapter-onepassword_connect

This adapter integrates with system described as: 1passwordConnect.

3
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 PlatformAutomationIntegrationAdapter1PasswordConnectPre-Release

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:preinstall AI (install-scripts): Standard Itential adapter setup hook; runs node utils/setup.js for git hook installation, consistent across all @itentialopensource adapters. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require in adapter.js loads adapterBase.js via path.join(__dirname,...) — deterministic path, not user-controlled. Stable pattern across Itential adapters. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in adapterBase.js for adapter framework utilities; consistent with the @itentialopensource adapter-utils base class pattern. ai
phantom-deps phantom-dep:ping AI (phantom-deps): ping is used in connectivity/troubleshoot scripts referenced in config, not directly imported in main code. False positive for this adapter pattern. ai
phantom-deps phantom-dep:prompts AI (phantom-deps): prompts used in utility scripts (tbScript.js etc.), not main adapter code. False positive for this adapter pattern. ai
phantom-deps phantom-dep:mocha-param AI (phantom-deps): mocha-param is a test dependency referenced in test config files; not imported in main code. False positive. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.3 15 / 6
1.0.2 15 / 6
1.0.1 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.2

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.

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.