@zeedhi/vue
Zeedhi indirection for VueJS
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:lodash.set | AI (dependencies): lodash.set is a well-known, widely-used utility; stable false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped @zeedhi/vue package; not a typosquat of vite — different namespace and purpose. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @zeedhi/vue package; not a typosquat of yup — different namespace and purpose. | ai | |
| phantom-deps | phantom-dep:node-sass | AI (phantom-deps): node-sass listed as runtime dep but used only in build config; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.0.11 | 5 / 4 | |
| 3.0.10 | 8 / 1 | |
| 3.0.9 | 8 / 1 | |
| 1.128.0 | 5 / 2 | |
| 1.126.0 | 5 / 2 | |
| 1.121.0 | 5 / 2 | |
| 1.116.0 | 5 / 2 | |
| 1.115.0 | 5 / 2 | |
| 1.109.1 | 5 / 2 | |
| 1.107.3 | 5 / 2 |
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
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.126.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. Consider requesting the maintainer enable provenance via CI/CD.
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.115.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.107.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.