@dereekb/zoho
@dereekb/zoho =======
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): @dereekb/zoho is a Zoho API integration package, not a typosquat of zod; scoped namespace makes impersonation implausible. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Fires in minified CLI bundle output; no actual base64 decode call visible in sample, pattern match on bundled code. | ai |
Versions (showing 7 of 109)
| Version | Deps | Published |
|---|---|---|
| 12.6.1 | 0 / 0 | |
| 12.6.0 | 0 / 0 | |
| 12.5.10 | 0 / 0 | |
| 12.5.9 | 0 / 0 | |
| 12.5.8 | 0 / 0 | |
| 12.5.7 | 0 / 0 | |
| 12.5.6 | 0 / 0 |
v12.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.