@vue/compat
Vue 3 compatibility build for Vue 2
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Migrated from personal npm account to GitHub Actions CI/CD; SLSA provenance confirms vuejs/core origin. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Compat layer publishes lag behind core Vue; dormancy is expected for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): yyx990803 is Evan You, Vue.js creator — not spam. Inflated semver is expected for monorepo sub-packages versioned to match the umbrella project. Both signals are false positives for this package. | ai | |
| dependencies | unvetted-dep:source-map-js | AI (dependencies): source-map-js is a well-known source map library; its use in Vue build tooling is expected and benign. | ai |
Versions (showing 51 of 95)
| Version | Deps | Published |
|---|---|---|
| 3.5.40 | 4 / 0 | |
| 3.5.39 | 4 / 0 | |
| 3.5.38 | 4 / 0 | |
| 3.5.35 | 4 / 0 | |
| 3.5.34 | 4 / 0 | |
| 3.5.33 | 4 / 0 | |
| 3.5.32 | 4 / 0 | |
| 3.5.31 | 4 / 0 | |
| 3.5.30 | 4 / 0 | |
| 3.5.29 | 3 / 0 | |
| 3.5.28 | 3 / 0 | |
| 3.5.27 | 3 / 0 | |
| 3.5.26 | 3 / 0 | |
| 3.5.25 | 3 / 0 | |
| 3.5.24 | 3 / 0 | |
| 3.5.23 | 3 / 0 | |
| 3.5.22 | 3 / 0 | |
| 3.5.21 | 3 / 0 | |
| 3.5.20 | 3 / 0 | |
| 3.5.19 | 3 / 0 | |
| 3.5.18 | 3 / 0 | |
| 3.5.17 | 3 / 0 | |
| 3.5.16 | 3 / 0 | |
| 3.5.15 | 3 / 0 | |
| 3.5.14 | 3 / 0 | |
| 3.5.13 | 3 / 0 | |
| 3.5.12 | 3 / 0 | |
| 3.5.11 | 3 / 0 | |
| 3.5.10 | 3 / 0 | |
| 3.5.9 | 3 / 0 | |
| 3.5.8 | 3 / 0 | |
| 3.5.7 | 3 / 0 | |
| 3.5.6 | 3 / 0 | |
| 3.5.5 | 3 / 0 | |
| 3.5.4 | 3 / 0 | |
| 3.5.3 | 3 / 0 | |
| 3.5.2 | 3 / 0 | |
| 3.5.1 | 3 / 0 | |
| 3.5.0 | 3 / 0 | |
| 3.4.38 | 3 / 0 | |
| 3.4.37 | 3 / 0 | |
| 3.4.36 | 3 / 0 | |
| 3.4.35 | 3 / 0 | |
| 3.4.34 | 3 / 0 | |
| 3.4.33 | 3 / 0 | |
| 3.4.32 | 3 / 0 | |
| 3.4.31 | 3 / 0 | |
| 3.4.30 | 3 / 0 | |
| 3.4.29 | 3 / 0 | |
| 3.4.28 | 3 / 0 | |
| 3.4.27 | 3 / 0 |
v3.5.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.