@vue/reactivity MIT 72 versions

@vue/reactivity

npm Repository Homepage

@vue/reactivity

72

Versions

MIT

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

yyx990803

Keywords

vue

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Vue.js core migrated to GitHub Actions for automated, SLSA-attested npm publishing. The yyx990803 → GitHub Actions transition is a legitimate, expected CI/CD automation change for the vuejs/core monorepo.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): yyx990803 is Evan You, creator of Vue.js — not a spam publisher. The spam flag is a false positive. Empty description is cosmetic only.	ai	2026/04/23

Versions (showing 72 of 172)

Hide prereleases

Version	Deps	Published
3.2.36	1 / 0	2022-05-23
3.2.35	1 / 0	2022-05-20
3.2.34	1 / 0	2022-05-19
3.2.33	1 / 0	2022-04-14
3.2.32	1 / 0	2022-04-12
3.2.31	1 / 0	2022-02-12
3.2.30	1 / 0	2022-02-07
3.2.29	1 / 0	2022-01-23
3.2.28	1 / 0	2022-01-21
3.2.27	1 / 0	2022-01-16
3.2.26	1 / 0	2021-12-12
3.2.25	1 / 0	2021-12-12
3.2.24	1 / 0	2021-12-06
3.2.23	1 / 0	2021-11-26
3.2.22	1 / 0	2021-11-15
3.2.21	1 / 0	2021-11-02
3.2.20	1 / 0	2021-10-08
3.2.19	1 / 0	2021-09-25
3.2.18	1 / 0	2021-09-24
3.2.17	1 / 0	2021-09-24
3.2.16	1 / 0	2021-09-23
3.2.15	1 / 0	2021-09-23
3.2.14	1 / 0	2021-09-22
3.2.13	1 / 0	2021-09-21
3.2.12	1 / 0	2021-09-17
3.2.11	1 / 0	2021-09-08
3.2.10	1 / 0	2021-09-07
3.2.9	1 / 0	2021-09-05
3.2.8	1 / 0	2021-09-02
3.2.7	1 / 0	2021-09-01
3.2.6	1 / 0	2021-08-24
3.2.5	1 / 0	2021-08-24
3.2.4	1 / 0	2021-08-17
3.2.3	1 / 0	2021-08-16
3.2.2	1 / 0	2021-08-11
3.2.1	1 / 0	2021-08-09
3.2.0	1 / 0	2021-08-09
3.1.5	1 / 0	2021-07-16
3.1.4	1 / 0	2021-07-02
3.1.3	1 / 0	2021-07-01
3.1.2	1 / 0	2021-06-22
3.1.1	1 / 0	2021-06-07
3.1.0	1 / 0	2021-06-07
3.0.11	1 / 0	2021-04-01
3.0.10	1 / 0	2021-03-31
3.0.9	1 / 0	2021-03-27
3.0.8	1 / 0	2021-03-26
3.0.7	1 / 0	2021-03-01
3.0.6	1 / 0	2021-02-24
3.0.5	1 / 0	2020-12-30
3.0.4	1 / 0	2020-12-02
3.0.3	1 / 0	2020-11-25
3.0.2	1 / 0	2020-10-20
3.0.1	1 / 0	2020-10-15
3.0.0	1 / 0	2020-09-18
3.6.0-beta.9	1 / 0	2026-03-26
3.6.0-beta.8	1 / 0	2026-03-16
3.6.0-beta.7	1 / 0	2026-02-27
3.6.0-beta.6	1 / 0	2026-02-12
3.6.0-beta.5	1 / 0	2026-01-30
3.6.0-beta.4	1 / 0	2026-01-23
3.6.0-beta.3	1 / 0	2026-01-12
3.6.0-beta.2	1 / 0	2026-01-04
3.6.0-beta.10	1 / 0	2026-04-13
3.6.0-beta.1	1 / 0	2025-12-23
3.6.0-alpha.7	1 / 0	2025-12-12
3.6.0-alpha.6	1 / 0	2025-12-04
3.6.0-alpha.5	1 / 0	2025-11-25
3.6.0-alpha.4	1 / 0	2025-11-14
3.6.0-alpha.3	1 / 0	2025-11-06
3.6.0-alpha.2	1 / 0	2025-07-18
3.6.0-alpha.1	1 / 0	2025-07-12

v3.2.36

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.

v3.2.35

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.

v3.2.34

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.

v3.2.33

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.

v3.2.32

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.

v3.2.31

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.

v3.2.30

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.

v3.2.29

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.

v3.2.28

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.

v3.2.27

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.

v3.2.26

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.

v3.2.25

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.

v3.2.24

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.

v3.2.23

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.

v3.2.22

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.

v3.2.21

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.

v3.2.20

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.

v3.2.19

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.

v3.2.18

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.

v3.2.17

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.

v3.2.16

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.

v3.2.15

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.

v3.2.14

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.

v3.2.13

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.

v3.2.12

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.

v3.2.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.

v3.2.10

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.

v3.2.9

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.

v3.2.8

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.

v3.2.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.

v3.2.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.

v3.2.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.

v3.2.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.

v3.2.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.

v3.2.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.

v3.2.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.

v3.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.

v3.1.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.

v3.1.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.

v3.1.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.

v3.1.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.

v3.1.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.

v3.1.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.

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

v3.0.10

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.

v3.0.9

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.

v3.0.8

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.

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

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

v3.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.

v3.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.

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

v3.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.

v3.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.

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