vue-demi MIT 37 versions

vue-demi

npm Repository Homepage

<p align="center"> <img src="https://github.com/vueuse/vue-demi/blob/main/assets/banner.png?raw=true" width="600"/> <br> <a href='https://www.npmjs.com/package/vue-demi'><img src='https://img.shields.io/npm/v/vue-demi?color=42b883' alt='npm'></a> </p>

37

Versions

MIT

License

Yes

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

posvaantfu

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): posva (Eduardo San Martin Morote) is a Vue.js core team member and legitimate co-maintainer of vue-demi alongside antfu.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): posva is a well-known Vue.js core team member added as a legitimate co-maintainer.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): vue-demi's postinstall uses execSync to detect Vue version and configure compatibility shims — a documented, stable design pattern for this package across all versions.	ai	2026/04/24
install-scripts	install-script:postinstall	AI (install-scripts): vue-demi's postinstall is its core Vue 2/3 compatibility-switching mechanism, documented and stable across all 88 versions. Not malicious.	ai	2026/04/23
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in loadModule() is used to probe for installed Vue peer dependencies (vue, @vue/composition-api). Standard peer-dep detection pattern, not arbitrary code loading.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): antfu (Anthony Fu) is a Vue core team member with a well-established open-source track record. The spam flag is a false positive for this publisher.	ai	2026/04/23

Versions (showing 37 of 37)

Version	Deps	Published
0.14.6	0 / 0	2023-08-28
0.14.5	0 / 0	2023-05-18
0.14.3	0 / 0	2023-05-17
0.14.2	0 / 0	2023-05-17
0.14.1	0 / 0	2023-05-09
0.13.10	0 / 0	2022-08-24
0.13.4	0 / 0	2022-07-12
0.13.3	0 / 0	2022-07-12
0.13.0	0 / 0	2022-05-31
0.12.4	0 / 0	2022-03-16
0.12.0	0 / 0	2021-10-27
0.11.4	0 / 0	2021-09-05
0.11.2	0 / 0	2021-07-15
0.11.1	0 / 0	2021-07-15
0.10.1	0 / 0	2021-07-09
0.7.4	0 / 0	2021-03-22
0.6.1	0 / 3	2021-02-25
0.5.3	0 / 0	2020-12-17
0.5.0	0 / 0	2020-12-16
0.4.5	0 / 0	2020-11-20
0.4.3	0 / 0	2020-11-09
0.4.1	0 / 0	2020-10-23
0.3.1	0 / 0	2020-08-23
0.3.0	0 / 1	2020-08-23
0.2.0	1 / 1	2020-08-04
0.1.11	0 / 2	2020-08-04
0.1.8	0 / 2	2020-08-04
0.1.7	0 / 2	2020-08-04
0.1.6	0 / 2	2020-08-04
0.1.3	0 / 2	2020-07-03
0.1.0	0 / 2	2020-07-01
0.0.7	0 / 2	2020-07-01
0.0.6	0 / 2	2020-07-01
0.0.5	0 / 2	2020-07-01
0.0.4	0 / 2	2020-07-01
0.0.2	0 / 2	2020-07-01
0.0.1	0 / 2	2020-07-01

v0.14.6

2 findings

HIGH Publisher changed: antfu → posva (on 2023-08-28) provenance

This version was published by a different npm account than previous versions on 2023-08-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.14.5

1 finding

LOW No provenance attestation provenance

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

v0.14.3

1 finding

LOW No provenance attestation provenance

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

v0.14.2

1 finding

LOW No provenance attestation provenance

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

v0.14.1

1 finding

LOW No provenance attestation provenance

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

v0.13.10

1 finding

LOW No provenance attestation provenance

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

v0.13.4

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.4

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.4

1 finding

LOW No provenance attestation provenance

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

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.5.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: antfu.

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.3

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.

v0.4.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.

v0.3.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: antfu.

LOW No provenance attestation provenance

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

v0.3.0

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.

v0.2.0

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.

v0.1.11

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.

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

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.

v0.1.6

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.

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

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.

v0.0.4

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.

v0.0.2

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.

v0.0.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.