@electerm/electerm-react
react components src for electerm
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Reference is in a JSDoc comment explaining how to list users on Linux — not runtime credential access. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 localhost proxy example in a UI config array — not an exfiltration endpoint. | ai |
Versions (showing 51 of 76)
| Version | Deps | Published |
|---|---|---|
| 3.15.39 | 0 / 0 | |
| 3.15.38 | 0 / 0 | |
| 3.15.37 | 0 / 0 | |
| 3.15.36 | 0 / 0 | |
| 3.15.35 | 0 / 0 | |
| 3.15.32 | 0 / 0 | |
| 3.15.28 | 0 / 0 | |
| 3.15.0 | 0 / 0 | |
| 3.12.0 | 0 / 0 | |
| 3.11.12 | 0 / 0 | |
| 3.11.11 | 0 / 0 | |
| 3.11.0 | 0 / 0 | |
| 3.10.0 | 0 / 0 | |
| 3.9.15 | 0 / 0 | |
| 3.9.5 | 0 / 0 | |
| 3.8.15 | 0 / 0 | |
| 3.8.8 | 0 / 0 | |
| 3.8.6 | 0 / 0 | |
| 3.7.18 | 0 / 0 | |
| 3.7.16 | 0 / 0 | |
| 3.7.9 | 0 / 0 | |
| 3.6.16 | 0 / 0 | |
| 3.6.6 | 0 / 0 | |
| 3.5.6 | 0 / 0 | |
| 3.3.8 | 0 / 0 | |
| 3.2.0 | 0 / 0 | |
| 3.1.26 | 0 / 0 | |
| 3.1.16 | 0 / 0 | |
| 3.1.6 | 0 / 0 | |
| 3.0.18 | 0 / 0 | |
| 3.0.6 | 0 / 0 | |
| 2.17.16 | 0 / 0 | |
| 2.17.8 | 0 / 0 | |
| 2.16.9 | 0 / 0 | |
| 2.16.8 | 0 / 0 | |
| 2.16.6 | 0 / 0 | |
| 2.15.8 | 0 / 0 | |
| 2.13.6 | 0 / 0 | |
| 2.13.0 | 0 / 0 | |
| 2.12.0 | 0 / 0 | |
| 2.11.16 | 0 / 0 | |
| 2.11.6 | 0 / 0 | |
| 2.10.27 | 0 / 0 | |
| 2.10.26 | 0 / 0 | |
| 2.10.6 | 0 / 0 | |
| 2.8.16 | 0 / 0 | |
| 2.8.8 | 0 / 0 | |
| 2.8.7 | 0 / 0 | |
| 2.8.6 | 0 / 0 | |
| 2.7.9 | 0 / 0 | |
| 2.7.8 | 0 / 0 |
v3.15.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.9
3 findingsAccessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/electerm/electerm/blob/6256511ee210feda572f9e2ae281a1dcacac7db3/client/components/sftp/owner-list.js#L6 4 | * for mac list users: `dscl . -list /Users UniqueID` 5 | * for mac list groups: `dscl . list /Groups PrimaryGroupID` > 6 | * for linux list users: `cat /etc/passwd` 7 | * for linux list groups: `cat /etc/group` 8 | * for windows list users: do not know yet
Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux Source: https://github.com/electerm/electerm/blob/6256511ee210feda572f9e2ae281a1dcacac7db3/client/components/sftp/owner-list.js#L27 25 | } 26 | > 27 | const linuxListUser = 'cat /etc/passwd' 28 | const linuxListGroup = 'cat /etc/group' 29 |
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.