@open-mercato/ui
Composable UI toolkit for Open Mercato backoffice and business apps.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Fires only in a test file snapshotting process.env for afterEach restoration — standard Jest pattern, not a runtime secret leak. | ai | |
| provenance | missing-githead | AI (provenance): Package has SLSA provenance attestation; missing gitHead is superseded by stronger CI/CD integrity signal. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @open-mercato/ui is not a plausible typosquat of qs; Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @open-mercato/ui is not a plausible typosquat of uuid; Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @open-mercato/ui is not a plausible typosquat of yup; Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @open-mercato/ui is not a plausible typosquat of joi; Levenshtein match is spurious. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @open-mercato/ui is not a plausible typosquat of pg; Levenshtein match is spurious. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 15 / 13 | |
| 0.6.2 | 15 / 13 | |
| 0.6.1 | 15 / 13 | |
| 0.6.0 | 14 / 8 | |
| 0.5.0 | 10 / 8 | |
| 0.4.10 | 6 / 8 | |
| 0.4.9 | 6 / 8 | |
| 0.4.8 | 6 / 8 | |
| 0.4.7 | 6 / 8 | |
| 0.4.6 | 7 / 7 | |
| 0.4.5 | 7 / 7 |
v0.6.3
2 findingsSpreading entire process.env into an object — may capture all secrets 7 | } from '../date-format' 8 | > 9 | const ORIGINAL_ENV = { ...process.env } 10 | 11 | afterEach(() => {
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
2 findingsSpreading entire process.env into an object — may capture all secrets 7 | } from '../date-format' 8 | > 9 | const ORIGINAL_ENV = { ...process.env } 10 | 11 | afterEach(() => {
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: piotrkarwatka.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: piotrkarwatka.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.