← Home

@scm-manager/ui-components

npm Repository

UI Components for SCM-Manager and its plugins

27
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, so a manually published version cannot be tied back to a reviewed commit.

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 27 of 27)

Version Deps Published
3.11.10 20 / 39
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.8.0 20 / 39
3.7.8 20 / 38
3.7.7 20 / 38
3.7.6 20 / 38
3.7.5 20 / 38
3.7.4 20 / 38
3.7.3 20 / 38
3.7.2 20 / 38
3.7.1 20 / 38
3.7.0 20 / 38
3.6.1 20 / 38
3.6.0 20 / 38

v3.8.0

1 finding
LOW No provenance attestation provenance

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

v3.7.5

1 finding
LOW No provenance attestation provenance

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

v3.7.4

1 finding
LOW No provenance attestation provenance

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

v3.7.3

1 finding
LOW No provenance attestation provenance

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

v3.7.2

1 finding
LOW No provenance attestation provenance

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

v3.7.1

1 finding
LOW No provenance attestation provenance

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

v3.7.0

1 finding
LOW No provenance attestation provenance

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

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