@dotenvx/dotenvx
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@dotenvx/tooling | AI (dependencies): First-party @dotenvx-scoped package from the same maintainer/org. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): First-party scoped dependency replacing internal logic, not an unvetted third party. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): patch-package postinstall, standard for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): clipboardy platform fallbacks (xsel/clipboard.exe), standard vendored deps. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') is a documented webpack-compat pattern for dynamic plugin resolution; stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Resolves optional dotenvx-pro plugin from project root; documented extension pattern, stable across versions. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in decryptKeyValue.js is part of ECIES-based .env encryption/decryption — core cryptographic feature of dotenvx. | ai | |
| typosquat | typosquat.levenshtein:dotenv | AI (typosquat): @dotenvx/dotenvx is the official scoped package from the original dotenv creator (@motdotla); it is not a typosquat of dotenv. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): dotenv is explicitly listed as a direct dependency in package.json; this is a false positive from the phantom-deps analyzer. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in decryptKeyValue.js is part of ECIES-based .env encryption/decryption — core cryptographic feature of dotenvx. | ai | |
| semgrep | semgrep:silent-process-exec | AI (semgrep): Detached spawn in ops.js is dotenvx's documented telemetry/ops feature, disabled via DOTENVX_NO_OPS=true. Not a reverse shell or miner. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same ops.js telemetry spawn as silent-process-exec; documented feature, not malicious. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into child process env is the core functionality of a dotenv CLI tool that injects env vars into subprocesses. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is required for a CLI tool that spawns subprocesses with injected environment variables — core functionality. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): child_process.spawn in ops.js is the documented telemetry/ops feature; not malicious. | ai |
Versions (showing 25 of 225)
| Version | Deps | Published |
|---|---|---|
| 1.11.1 | 9 / 8 | |
| 1.11.0 | 9 / 8 | |
| 1.10.4 | 9 / 8 | |
| 1.10.3 | 9 / 8 | |
| 1.10.2 | 9 / 8 | |
| 1.10.1 | 10 / 8 | |
| 1.10.0 | 10 / 8 | |
| 1.9.1 | 11 / 8 | |
| 1.9.0 | 11 / 8 | |
| 1.8.0 | 12 / 8 | |
| 1.7.0 | 13 / 8 | |
| 1.6.5 | 14 / 8 | |
| 1.6.4 | 14 / 8 | |
| 1.6.3 | 14 / 8 | |
| 1.6.2 | 14 / 8 | |
| 1.6.1 | 14 / 8 | |
| 1.6.0 | 14 / 8 | |
| 1.5.0 | 19 / 8 | |
| 1.4.0 | 20 / 8 | |
| 1.3.2 | 21 / 8 | |
| 1.3.0 | 21 / 8 | |
| 1.2.0 | 21 / 8 | |
| 1.1.0 | 20 / 7 | |
| 1.0.1 | 20 / 7 | |
| 1.0.0 | 21 / 7 |
v1.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.5.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
3 findingsScript: patch-package
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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
3 findingsScript: patch-package
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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
2 findingsPackage 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
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.