← Home

@scm-manager/ui-components

UI Components for SCM-Manager and its plugins

17
Versions
AGPL-3.0-only
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

sdorrapfeuffercesmarvinmatthias.thieroffavetgittidiegelertzerr

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Fires in test files using /etc/passwd as a path fixture, not credential harvesting. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IPs appear in URL validation test fixtures, not runtime network calls. ai
semgrep semgrep:shady-links-tlds AI (semgrep): Suspicious TLDs appear in URL validation test fixtures, not runtime code. ai

Versions (showing 17 of 17)

Version Deps Published
3.11.8 20 / 39
3.11.7 20 / 39
3.11.6 20 / 39
3.11.5 20 / 39
3.11.4 20 / 39
3.11.3 20 / 39
3.11.2 20 / 39
3.11.1 20 / 39
3.11.0 20 / 39
3.10.3 20 / 39
3.10.2 20 / 39
3.10.1 20 / 39
3.10.0 20 / 39
3.9.0 20 / 39
3.7.8 20 / 38
3.7.7 20 / 38
3.7.6 20 / 38

v3.11.8

9 findings
HIGH etc-passwd-access: src/repos/diffs.test.ts:53 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 51 | describe("getPath tests", () => { 52 | it("should pick the new path, for type add", () => { > 53 | const file = add("/etc/passwd"); 54 | const path = getPath(file); 55 | expect(path).toBe("/etc/passwd");

HIGH etc-passwd-access: src/repos/diffs.test.ts:55 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 53 | const file = add("/etc/passwd"); 54 | const path = getPath(file); > 55 | expect(path).toBe("/etc/passwd"); 56 | }); 57 |

HIGH etc-passwd-access: src/repos/diffs.test.ts:59 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 57 | 58 | it("should pick the old path, for type delete", () => { > 59 | const file = rm("/etc/passwd"); 60 | const path = getPath(file); 61 | expect(path).toBe("/etc/passwd");

HIGH etc-passwd-access: src/repos/diffs.test.ts:61 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 59 | const file = rm("/etc/passwd"); 60 | const path = getPath(file); > 61 | expect(path).toBe("/etc/passwd"); 62 | }); 63 | });

HIGH etc-passwd-access: src/repos/diffs.test.ts:67 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 65 | describe("createHunkIdentifier tests", () => { 66 | it("should create identifier", () => { > 67 | const file = modify("/etc/passwd"); 68 | const hunk = createHunk("@@ -1,18 +1,15 @@"); 69 | const identifier = createHunkIdentifier(file, hunk);

HIGH etc-passwd-access: src/repos/diffs.test.ts:70 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 68 | const hunk = createHunk("@@ -1,18 +1,15 @@"); 69 | const identifier = createHunkIdentifier(file, hunk); > 70 | expect(identifier).toBe("modify_/etc/passwd_@@ -1,18 +1,15 @@"); 71 | }); 72 | });

HIGH etc-passwd-access: src/repos/diffs.test.ts:77 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 75 | it("should create identifier", () => { 76 | const identifier = createHunkIdentifierFromContext({ > 77 | file: rm("/etc/passwd"), 78 | hunk: createHunk("@@ -1,42 +1,39 @@"), 79 | });

HIGH etc-passwd-access: src/repos/diffs.test.ts:80 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 78 | hunk: createHunk("@@ -1,42 +1,39 @@"), 79 | }); > 80 | expect(identifier).toBe("delete_/etc/passwd_@@ -1,42 +1,39 @@"); 81 | }); 82 | });

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.

v3.11.7

1 finding
LOW No provenance attestation provenance

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

v3.11.6

1 finding
LOW No provenance attestation provenance

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

v3.11.5

1 finding
LOW No provenance attestation provenance

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

v3.11.4

1 finding
LOW No provenance attestation provenance

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

v3.11.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.

v3.11.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.

v3.11.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.

v3.11.0

1 finding
LOW No provenance attestation provenance

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

v3.10.3

1 finding
LOW No provenance attestation provenance

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

v3.10.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.

v3.10.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.

v3.10.0

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.

v3.9.0

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.

v3.7.8

1 finding
LOW No provenance attestation provenance

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

v3.7.7

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.

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