@scm-manager/ui-plugins
Defines the versions of SCM-Manager plugin dependencies provided by the core webapp. Exclusively used by the postinstall command of @scm-manager/plugin-scripts.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:redux | AI (phantom-deps): Intentionally listed in lazyDependencies; declared but not directly imported by design. | ai | |
| phantom-deps | phantom-dep:react-redux | AI (phantom-deps): Intentionally listed in lazyDependencies; declared but not directly imported by design. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.11.10 | 20 / 17 | |
| 3.11.8 | 20 / 17 | |
| 3.11.7 | 20 / 17 | |
| 3.11.6 | 20 / 17 | |
| 3.11.5 | 20 / 17 | |
| 3.11.4 | 20 / 17 | |
| 3.11.3 | 20 / 17 | |
| 3.11.2 | 20 / 17 | |
| 3.11.1 | 20 / 17 | |
| 3.11.0 | 20 / 17 | |
| 3.10.3 | 20 / 17 | |
| 3.10.2 | 20 / 17 | |
| 3.10.1 | 20 / 17 | |
| 3.10.0 | 20 / 17 | |
| 3.9.0 | 20 / 17 | |
| 3.7.8 | 20 / 17 | |
| 3.7.7 | 20 / 17 | |
| 3.7.6 | 20 / 17 |
v3.11.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pfeuffer) than the most recent previously approved version (cesmarvin) on 2026-06-10, but pfeuffer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.11.8
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
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.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. Consider requesting the maintainer enable provenance via CI/CD.