← Home

@wellau/sslvpn

npm Repository Homepage

Wellau SSL VPN desktop maintenance tools for OpenConnect, tray status, and guarded reconnects.

6
Versions
UNLICENSED
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

sd4494093

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env-spread is used to pass environment to a child VPN connect subprocess — standard launcher pattern, not exfiltration. ai

Versions (showing 6 of 6)

Version Deps Published
0.2.0 0 / 0
0.1.4 0 / 0
0.1.3 0 / 0
0.1.2 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0

v0.2.0

3 findings
HIGH env-spread: bin/wellau-vpn-watchdog.js:109 semgrep

Spreading entire process.env into an object — may capture all secrets Source: ssh://[email protected]/sd4494094/sslvpn/blob/e59e3c0e344855cd39e7289736ea477eea368c92/bin/wellau-vpn-watchdog.js#L109 107 | 108 | const connectScript = path.join(__dirname, "wellau-vpn-connect-env.js"); > 109 | const extraEnv = { 110 | ...process.env, 111 | WELLAU_VPN_NONINTERACTIVE_SUDO: process.platform === "win32" ? process.env.WELLAU_VPN_NONINTERACTIVE_SUDO || "0" : "1"

HIGH env-spread: lib/common.js:69 semgrep

Spreading entire process.env into an object — may capture all secrets Source: ssh://[email protected]/sd4494094/sslvpn/blob/e59e3c0e344855cd39e7289736ea477eea368c92/lib/common.js#L69 67 | const envFile = process.env.WELLAU_SSLVPN_ENV_FILE || runtimeEnv.WELLAU_SSLVPN_ENV_FILE || path.join(configDir, ".env" 68 | const fileEnv = parseEnvFile(envFile); > 69 | const merged = { 70 | ...runtimeEnv, 71 | ...fileEnv,

LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.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.