@scm-manager/ui-components
UI Components for SCM-Manager and its plugins
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): 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 findingsAccessing /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");
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 |
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");
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 | });
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);
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 | });
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 | });
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 | });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.