@zeedhi/common
Zeedhi Common
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript listed as runtime dep for type resolution in a TS-first package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:lodash.set | AI (dependencies): lodash.set is a well-known, stable utility; pinned to 4.3.* with no active advisories. | ai | |
| phantom-deps | phantom-dep:@types/lodash.clonedeep | AI (phantom-deps): @types packages are type-only and commonly declared without direct import; stable false positive for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 3.0.6 | 9 / 10 | |
| 1.128.0 | 9 / 9 | |
| 1.127.0 | 9 / 9 | |
| 1.126.0 | 9 / 9 | |
| 1.124.0 | 9 / 9 | |
| 1.121.0 | 9 / 9 | |
| 1.120.2 | 9 / 9 | |
| 1.117.0 | 9 / 9 | |
| 1.116.0 | 9 / 9 | |
| 1.114.0 | 9 / 9 | |
| 1.112.0 | 9 / 9 | |
| 1.110.1 | 9 / 9 | |
| 1.110.0 | 9 / 9 | |
| 1.109.1 | 9 / 9 | |
| 1.109.0 | 9 / 9 | |
| 1.108.1 | 9 / 9 | |
| 1.108.0 | 9 / 9 | |
| 1.107.3 | 9 / 9 | |
| 1.107.1 | 9 / 9 | |
| 1.97.6 | 9 / 9 |
v3.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.128.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.127.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.126.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.124.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.121.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.120.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.117.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.116.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.114.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.112.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.110.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.110.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.109.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.109.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.108.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.107.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.107.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.97.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.