← Home

@dotenvx/dotenvx-ops

npm Repository Homepage

Secrets for agents–from the creator of `dotenv` and `dotenvx`

51
Versions
See 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

motdotenvmotdotla

Keywords

dotenvdotenvxopsarmorenv

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs a local Node.js script (src/cli/postinstall.js) for CLI setup — standard pattern for this dotenvx ecosystem tool, no network fetch or obfuscation. ai
semgrep semgrep:env-spread AI (semgrep): env spread in clipboardy/macos.js is to pass LC_CTYPE=UTF-8 to a subprocess — standard locale handling for clipboard operations, not credential exfiltration. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in device.js is for ECIES cryptographic key handling — core to this secrets management package's legitimate functionality. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding in decryptValue.js is for decrypting ciphertext — core cryptographic operation for this secrets management package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in playwrightConnect.js to install Chromium via npx playwright install — standard Playwright setup pattern, not arbitrary code execution. ai
npm-metadata bundled-binaries AI (npm-metadata): Bundled binaries are xsel (Linux) and clipboard utilities (Windows) from clipboardy fallbacks — well-known clipboard access utilities, not backdoors. ai

Versions (showing 51 of 65)

View all versions
Version Deps Published
0.54.0 16 / 7
0.53.2 16 / 7
0.53.1 16 / 7
0.53.0 16 / 7
0.52.1 16 / 7
0.52.0 16 / 7
0.51.1 16 / 7
0.51.0 16 / 7
0.50.1 16 / 7
0.50.0 16 / 7
0.49.2 16 / 7
0.49.1 16 / 7
0.49.0 16 / 7
0.48.3 16 / 7
0.48.2 16 / 7
0.48.1 16 / 7
0.48.0 16 / 7
0.47.0 16 / 7
0.46.1 16 / 7
0.46.0 16 / 7
0.45.3 16 / 7
0.45.2 16 / 7
0.45.1 16 / 7
0.45.0 16 / 7
0.44.0 16 / 7
0.43.0 16 / 7
0.42.1 16 / 7
0.42.0 16 / 7
0.41.0 16 / 7
0.40.0 16 / 7
0.39.1 16 / 7
0.39.0 16 / 7
0.38.3 16 / 7
0.38.2 16 / 7
0.38.1 16 / 7
0.38.0 16 / 7
0.37.9 15 / 7
0.37.8 15 / 7
0.37.7 15 / 7
0.37.6 15 / 6
0.37.5 15 / 6
0.37.4 14 / 6
0.37.3 14 / 6
0.37.2 14 / 6
0.37.0 14 / 6
0.23.7 13 / 6
0.23.6 13 / 6
0.23.4 13 / 6
0.23.3 13 / 6
0.23.2 13 / 6
0.23.1 13 / 6

v0.54.0

1 finding
LOW No provenance attestation provenance

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

v0.53.2

1 finding
LOW No provenance attestation provenance

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

v0.53.1

1 finding
LOW No provenance attestation provenance

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

v0.53.0

1 finding
LOW No provenance attestation provenance

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

v0.52.1

1 finding
LOW No provenance attestation provenance

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

v0.52.0

1 finding
LOW No provenance attestation provenance

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

v0.51.1

1 finding
LOW No provenance attestation provenance

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

v0.51.0

1 finding
LOW No provenance attestation provenance

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

v0.50.1

1 finding
LOW No provenance attestation provenance

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

v0.50.0

1 finding
LOW No provenance attestation provenance

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

v0.49.2

1 finding
LOW No provenance attestation provenance

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

v0.49.1

1 finding
LOW No provenance attestation provenance

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

v0.49.0

1 finding
LOW No provenance attestation provenance

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

v0.48.3

1 finding
LOW No provenance attestation provenance

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

v0.48.2

1 finding
LOW No provenance attestation provenance

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

v0.48.1

1 finding
LOW No provenance attestation provenance

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

v0.48.0

1 finding
LOW No provenance attestation provenance

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

v0.47.0

1 finding
LOW No provenance attestation provenance

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

v0.46.1

1 finding
LOW No provenance attestation provenance

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

v0.46.0

1 finding
LOW No provenance attestation provenance

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

v0.45.3

1 finding
LOW No provenance attestation provenance

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

v0.45.2

1 finding
LOW No provenance attestation provenance

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

v0.45.1

1 finding
LOW No provenance attestation provenance

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

v0.45.0

1 finding
LOW No provenance attestation provenance

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

v0.44.0

1 finding
LOW No provenance attestation provenance

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

v0.43.0

1 finding
LOW No provenance attestation provenance

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

v0.42.1

1 finding
LOW No provenance attestation provenance

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

v0.40.0

3 findings
HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • src/lib/helpers/clipboardy/fallbacks/linux/xsel • src/lib/helpers/clipboardy/fallbacks/windows/clipboard_i686.exe • src/lib/helpers/clipboardy/fallbacks/windows/clipboard_x86_64.exe

HIGH env-spread: src/lib/helpers/clipboardy/macos.js:4 semgrep

Spreading entire process.env into an object — may capture all secrets Source: https://github.com/dotenvx/dotenvx-ops/blob/ae49b8da740cddb9c7df3867e4c6a6d0f26f494c/src/lib/helpers/clipboardy/macos.js#L4 2 | const execa = require('execa') 3 | > 4 | const env = { 5 | ...process.env, 6 | LC_CTYPE: 'UTF-8'

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.39.1

1 finding
LOW No provenance attestation provenance

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

v0.39.0

1 finding
LOW No provenance attestation provenance

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

v0.38.3

1 finding
LOW No provenance attestation provenance

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

v0.38.2

1 finding
LOW No provenance attestation provenance

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

v0.38.1

1 finding
LOW No provenance attestation provenance

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

v0.38.0

1 finding
LOW No provenance attestation provenance

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

v0.37.9

1 finding
LOW No provenance attestation provenance

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

v0.37.8

1 finding
LOW No provenance attestation provenance

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

v0.37.7

1 finding
LOW No provenance attestation provenance

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

v0.37.6

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.

v0.37.5

1 finding
LOW No provenance attestation provenance

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

v0.37.4

1 finding
LOW No provenance attestation provenance

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

v0.37.3

1 finding
LOW No provenance attestation provenance

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

v0.37.2

1 finding
LOW No provenance attestation provenance

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

v0.37.0

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

Script: node ./src/cli/postinstall.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.23.7

1 finding
LOW No provenance attestation provenance

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

v0.23.6

1 finding
LOW No provenance attestation provenance

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

v0.23.4

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.

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

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

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