@open-mercato/shared
The shared foundation for Open Mercato packages.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal shared library for @open-mercato org; no public repo/homepage is expected for this pattern. | ai | |
| semgrep | semgrep:etc-passwd-access | AI (semgrep): Appears only in test asserting /etc/passwd URLs are rejected by the URL safety validator — not credential harvesting. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): process.env spread is in a test fixture to save/restore env state, not to exfiltrate secrets. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IPs appear only in test cases asserting private IP URLs are rejected — expected pattern for a URL safety library. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is standard JWT payload parsing, not obfuscation or payload hiding. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.6.3 | 10 / 4 | |
| 0.6.2 | 10 / 4 | |
| 0.6.0 | 9 / 4 | |
| 0.5.0 | 2 / 4 | |
| 0.4.10 | 1 / 3 | |
| 0.4.9 | 1 / 3 | |
| 0.4.8 | 1 / 3 | |
| 0.4.7 | 1 / 3 | |
| 0.4.6 | 1 / 3 | |
| 0.4.5 | 1 / 3 |
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
1 findingPublished 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
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.