@vue/reactivity-transform
@vue/reactivity-transform
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 | |
| 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 | |
| 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 |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.3.13 | 5 / 2 | |
| 3.3.12 | 5 / 2 | |
| 3.3.11 | 5 / 2 | |
| 3.3.10 | 5 / 2 | |
| 3.3.9 | 5 / 2 | |
| 3.3.8 | 5 / 2 | |
| 3.3.7 | 5 / 2 | |
| 3.3.6 | 5 / 2 | |
| 3.3.5 | 5 / 2 | |
| 3.3.4 | 5 / 2 | |
| 3.3.3 | 5 / 2 | |
| 3.3.2 | 5 / 2 | |
| 3.3.1 | 5 / 2 | |
| 3.3.0 | 5 / 2 | |
| 3.2.47 | 5 / 2 | |
| 3.2.46 | 5 / 2 | |
| 3.2.45 | 5 / 2 | |
| 3.2.44 | 5 / 2 | |
| 3.2.43 | 5 / 2 | |
| 3.2.42 | 5 / 2 | |
| 3.2.41 | 5 / 2 | |
| 3.2.40 | 5 / 2 | |
| 3.2.39 | 5 / 2 | |
| 3.2.38 | 5 / 2 | |
| 3.2.37 | 5 / 2 | |
| 3.2.36 | 5 / 2 | |
| 3.2.35 | 5 / 2 | |
| 3.2.34 | 5 / 2 | |
| 3.2.33 | 5 / 2 | |
| 3.2.32 | 5 / 2 | |
| 3.2.31 | 5 / 2 | |
| 3.2.30 | 5 / 2 | |
| 3.2.29 | 5 / 2 | |
| 3.2.28 | 5 / 2 | |
| 3.2.27 | 5 / 2 | |
| 3.2.26 | 5 / 2 | |
| 3.2.25 | 5 / 2 |
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.