@scm-manager/ui-buttons
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package; tiny payload, no description/repo are expected patterns for @scm-manager UI components. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is consistent across all @scm-manager/ui-* packages. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 3.11.10 | 1 / 3 | |
| 3.11.8 | 1 / 3 | |
| 3.11.1 | 1 / 3 | |
| 3.11.0 | 1 / 3 | |
| 3.10.3 | 1 / 3 | |
| 3.10.2 | 1 / 3 | |
| 3.10.1 | 1 / 3 | |
| 3.10.0 | 1 / 3 | |
| 3.9.0 | 1 / 3 | |
| 3.8.0 | 1 / 3 | |
| 3.7.7 | 1 / 3 | |
| 3.7.6 | 1 / 3 | |
| 3.7.5 | 1 / 3 | |
| 3.7.4 | 1 / 3 | |
| 3.7.3 | 1 / 3 | |
| 3.7.2 | 1 / 3 | |
| 3.7.1 | 1 / 3 | |
| 3.7.0 | 1 / 3 | |
| 3.6.1 | 1 / 3 | |
| 3.6.0 | 1 / 3 | |
| 3.5.0 | 0 / 3 | |
| 3.4.2 | 0 / 3 | |
| 3.4.1 | 0 / 3 | |
| 3.4.0 | 0 / 3 | |
| 3.3.0 | 0 / 3 | |
| 3.2.2 | 0 / 3 | |
| 3.2.1 | 0 / 3 | |
| 3.2.0 | 0 / 3 |
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
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.