@vue/reactivity-transform MIT 25 versions

@vue/reactivity-transform

npm Repository Homepage

@vue/reactivity-transform

25

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yyx990803

Keywords

vue

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-removed	AI (maintainer-change): Vue.js core team consolidated npm maintainers across the monorepo; yyx990803 (Evan You) remains the publisher. This is a known organizational change, not a takeover signal.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): False positive: @vue/reactivity-transform is a legitimate Vue.js core monorepo package. Spam-flagged maintainers are well-known Vue.js core contributors (Evan You et al.), not actual spammers.	ai	2026/04/23
dependencies	unvetted-dep:@vue/compiler-core	AI (dependencies): Pinned sibling package from the same Vue.js core monorepo release; expected dependency pattern for this package.	ai	2026/04/23

Versions (showing 25 of 25)

Version	Deps	Published
3.3.11	5 / 2	2023-12-08
3.3.10	5 / 2	2023-12-04
3.3.9	5 / 2	2023-11-25
3.3.5	5 / 2	2023-10-20
3.3.3	5 / 2	2023-05-18
3.3.2	5 / 2	2023-05-12
3.3.1	5 / 2	2023-05-11
3.2.46	5 / 2	2023-02-02
3.2.45	5 / 2	2022-11-11
3.2.44	5 / 2	2022-11-09
3.2.43	5 / 2	2022-11-09
3.2.42	5 / 2	2022-11-09
3.2.41	5 / 2	2022-10-14
3.2.39	5 / 2	2022-09-08
3.2.38	5 / 2	2022-08-30
3.2.37	5 / 2	2022-06-06
3.2.35	5 / 2	2022-05-20
3.2.34	5 / 2	2022-05-19
3.2.32	5 / 2	2022-04-12
3.2.31	5 / 2	2022-02-12
3.2.29	5 / 2	2022-01-23
3.2.28	5 / 2	2022-01-21
3.2.27	5 / 2	2022-01-16
3.2.26	5 / 2	2021-12-12
3.2.25	5 / 2	2021-12-12

v3.3.11

1 finding

LOW No provenance attestation provenance

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

v3.3.10

1 finding

LOW No provenance attestation provenance

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

v3.3.9

1 finding

LOW No provenance attestation provenance

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

v3.3.5

1 finding

LOW No provenance attestation provenance

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

v3.3.3

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.2.46

1 finding

LOW No provenance attestation provenance

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

v3.2.45

1 finding

LOW No provenance attestation provenance

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

v3.2.44

1 finding

LOW No provenance attestation provenance

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

v3.2.43

1 finding

LOW No provenance attestation provenance

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

v3.2.42

1 finding

LOW No provenance attestation provenance

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

v3.2.41

1 finding

LOW No provenance attestation provenance

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

v3.2.39

1 finding

LOW No provenance attestation provenance

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

v3.2.38

1 finding

LOW No provenance attestation provenance

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

v3.2.37

1 finding

LOW No provenance attestation provenance

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

v3.2.35

1 finding

LOW No provenance attestation provenance

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

v3.2.34

1 finding

LOW No provenance attestation provenance

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

v3.2.32

1 finding

LOW No provenance attestation provenance

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

v3.2.31

1 finding

LOW No provenance attestation provenance

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

v3.2.29

1 finding

LOW No provenance attestation provenance

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

v3.2.28

1 finding

LOW No provenance attestation provenance

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

v3.2.27

1 finding

LOW No provenance attestation provenance

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

v3.2.26

1 finding

LOW No provenance attestation provenance

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

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.