← Home

@zeedhi/vuetify

npm

Zeedhi Components based on Vuetify

51
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

zeedhi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Manual publish is normal for this package; 12% npm adoption rate makes this a common pattern. ai
phantom-deps phantom-dep:vue-property-decorator AI (phantom-deps): Component library re-exports Vue decorators; stable pattern across versions. ai
phantom-deps phantom-dep:@zeedhi/vue AI (phantom-deps): Same-org type-only/build dependency, not a supply-chain concern. ai
dependencies unvetted-dep:vue-grid-layout AI (dependencies): vue-grid-layout is a well-known Vue component; stable peer dep for this UI library across versions. ai
source-diff net-exec-file:dist/zd-vuetify.min.js AI (source-diff): Standard Vite browser bundle; network calls are UI component fetch patterns, not exfil or dropper behavior. ai
source-diff obfuscated-file:dist/zd-vuetify.mjs AI (source-diff): Long lines are minified Vite build output, not obfuscation; no _0x arrays or eval(atob()) patterns. ai
source-diff net-exec-file:dist/zd-vuetify.mjs AI (source-diff): Standard Vite ESM bundle; imports are from @zeedhi/common and @zeedhi/core, no hostile endpoints. ai
phantom-deps phantom-dep:lodash.isundefined AI (phantom-deps): Declared dep; config-only reference, stable FP. ai
phantom-deps phantom-dep:apexcharts AI (phantom-deps): Declared as bundled dep; referenced in config/build files, not directly imported in source — stable false positive for this package. ai
phantom-deps phantom-dep:vue-class-component AI (phantom-deps): Declared dep; config-only reference, stable FP. ai
phantom-deps phantom-dep:@panter/vue-i18next AI (phantom-deps): Declared dep; config-only reference, stable FP. ai
phantom-deps phantom-dep:sortablejs AI (phantom-deps): Same pattern: declared dep used transitively via component config, not direct import. ai
phantom-deps phantom-dep:vue-apexcharts AI (phantom-deps): Declared dep; phantom-dep heuristic fires on config-only references — stable FP. ai
phantom-deps phantom-dep:lodash.debounce AI (phantom-deps): Declared dep; config-only reference pattern, stable FP for this package. ai
phantom-deps phantom-dep:vue-grid-layout AI (phantom-deps): Declared dep; config-only reference, stable FP. ai
phantom-deps phantom-dep:lodash.camelcase AI (phantom-deps): Declared dep; config-only reference, stable FP. ai
phantom-deps phantom-dep:lodash.kebabcase AI (phantom-deps): Declared dep; config-only reference, stable FP. ai

Versions (showing 51 of 74)

View all versions
Version Deps Published
3.1.0 9 / 11
3.0.11 9 / 11
3.0.10 14 / 8
3.0.9 14 / 8
1.132.0 16 / 6
1.131.0 16 / 6
1.130.0 16 / 6
1.129.0 16 / 6
1.128.0 16 / 6
1.127.0 16 / 6
1.126.0 16 / 6
1.125.0 16 / 6
1.124.0 16 / 6
1.123.0 16 / 6
1.122.0 16 / 6
1.121.0 16 / 6
1.120.3 16 / 6
1.120.2 16 / 6
1.120.1 16 / 6
1.120.0 16 / 6
1.119.0 16 / 6
1.118.2 16 / 6
1.118.1 16 / 6
1.118.0 16 / 6
1.117.1 16 / 6
1.117.0 16 / 6
1.116.0 16 / 6
1.115.0 16 / 6
1.114.1 16 / 6
1.114.0 16 / 6
1.113.0 16 / 6
1.112.0 16 / 6
1.111.0 16 / 6
1.110.1 16 / 6
1.110.0 16 / 6
1.109.1 16 / 6
1.109.0 16 / 6
1.108.0 16 / 6
1.107.3 16 / 6
1.107.2 16 / 6
1.107.1 16 / 6
1.107.0 16 / 6
1.106.0 16 / 6
1.105.1 16 / 6
1.105.0 16 / 6
1.104.0 16 / 6
1.103.0 16 / 6
1.102.0 16 / 6
1.101.1 16 / 6
1.101.0 16 / 6
1.100.2 16 / 6

v3.1.0

4 findings
HIGH New file with network + code execution: dist/zd-vuetify.min.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: dist/zd-vuetify.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New file with network + code execution: dist/zd-vuetify.mjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.11

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.132.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.131.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.129.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.128.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.126.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.125.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.124.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.123.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.122.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.121.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.120.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.120.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.120.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.120.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.119.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.118.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.118.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.118.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.117.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.117.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.116.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.115.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.114.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.114.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.113.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.112.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.111.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.110.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.110.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.109.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.109.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.108.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.107.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.107.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.107.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.106.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.105.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.105.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.104.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.103.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.102.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.101.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.101.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.100.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.