@munchi_oy/sync-utils
Sync and cache utilities for Munchi services
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish environment change (manual publish by known maintainer munchi_dev); no other malicious indicators. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 0 / 7 | |
| 3.5.0 | 0 / 7 | |
| 3.3.0 | 0 / 7 | |
| 3.2.6 | 0 / 7 | |
| 3.2.4 | 0 / 7 | |
| 3.2.3 | 0 / 7 | |
| 3.2.2 | 0 / 5 | |
| 3.2.1 | 0 / 5 | |
| 3.2.0 | 0 / 5 | |
| 3.1.2 | 0 / 7 | |
| 3.1.1 | 0 / 7 | |
| 3.1.0 | 0 / 7 | |
| 3.0.0 | 0 / 5 | |
| 0.3.8 | 0 / 5 | |
| 0.3.7 | 0 / 5 | |
| 0.3.6 | 0 / 5 | |
| 0.3.4 | 0 / 5 | |
| 0.3.3 | 0 / 5 | |
| 0.3.2 | 0 / 5 | |
| 0.3.1 | 0 / 5 | |
| 0.1.2 | 0 / 0 | |
| 0.1.1 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (muhammad6920) than the most recent previously approved version (munchi_dev) on 2026-04-25, but muhammad6920 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.2.3
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: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
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: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.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: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.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: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
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: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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: muhammad6920.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: munchi_dev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (munchi_dev) than the most recent previously approved version (muhammad6920) on 2026-04-15, but munchi_dev 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.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: munchi_dev.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (munchi_dev) than the most recent previously approved version (muhammad6920) on 2026-04-15, but munchi_dev 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.