@vibecontrols/vibe-plugin-tool-ssh SEE LICENSE IN LICENSE 17 versions

@vibecontrols/vibe-plugin-tool-ssh

npm Repository Homepage

SSH connections, remote terminals, port forwarding & remote agent installation for VibeControls Agent

17

Versions

SEE LICENSE IN LICENSE

License

No

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

burdenoffcorp

Keywords

vibecontrolsvibevibe-pluginsshport-forwardremote-developmentelysiabun

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	bundled-binaries	AI (npm-metadata): Native .node files are ssh2/cpu-features build artifacts; expected for an SSH library using native crypto bindings.	ai	2026/05/27
phantom-deps	phantom-dep:ssh2	AI (phantom-deps): ssh2 is a runtime dep used via dynamic/bundled import in the minified dist; phantom-dep heuristic is a false positive here.	ai	2026/05/27

Versions (showing 17 of 17)

Version	Deps	Published
2026.601.1	2 / 11	2026-06-01
2026.530.3	2 / 11	2026-05-30
2026.530.2	2 / 11	2026-05-30
2026.530.1	2 / 11	2026-05-30
2026.529.1	2 / 11	2026-05-29
2026.528.2	2 / 11	2026-05-28
2026.528.1	2 / 11	2026-05-28
2026.525.2	2 / 11	2026-05-25
2026.525.1	2 / 11	2026-05-25
2026.522.1	2 / 11	2026-05-22
2026.518.1	2 / 11	2026-05-18
2026.512.1	2 / 11	2026-05-12
2026.510.1	2 / 11	2026-05-10
2026.509.1	2 / 11	2026-05-09
2026.508.3	2 / 11	2026-05-09
2026.508.2	1 / 11	2026-05-07
2026.428.4	1 / 11	2026-04-29

v2026.601.1

1 finding

LOW No provenance attestation provenance

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

v2026.530.3

1 finding

LOW No provenance attestation provenance

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

v2026.530.2

1 finding

LOW No provenance attestation provenance

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

v2026.530.1

1 finding

LOW No provenance attestation provenance

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

v2026.529.1

1 finding

LOW No provenance attestation provenance

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

v2026.528.2

1 finding

LOW No provenance attestation provenance

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

v2026.528.1

1 finding

LOW No provenance attestation provenance

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

v2026.525.2

1 finding

LOW No provenance attestation provenance

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

v2026.525.1

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/cpufeatures-86axn7bp.node • dist/sshcrypto-bbzvgpaq.node

LOW No provenance attestation provenance

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

v2026.522.1

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/cpufeatures-35tjfzct.node • dist/sshcrypto-3xszjg3c.node

LOW No provenance attestation provenance

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

v2026.518.1

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/cpufeatures-35tjfzct.node • dist/sshcrypto-3xszjg3c.node

LOW No provenance attestation provenance

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

v2026.512.1

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/cpufeatures-35tjfzct.node • dist/sshcrypto-3xszjg3c.node

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.

v2026.510.1

1 finding

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.

v2026.509.1

1 finding

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.

v2026.508.3

1 finding

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.

v2026.508.2

1 finding

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.

v2026.428.4

2 findings

HIGH Bundled binary files (2) npm-metadata

Package contains compiled binaries that could be backdoors: • dist/cpufeatures-8hc4bjx7.node • dist/sshcrypto-spk4rdny.node

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.