vue3-google-login
Add a Login with Google feature to your Vue 3 application using Google Identity Services
Supply chain provenance
Status for the latest visible version.
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
Keywords
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.1.4 | 0 / 29 | |
| 2.1.3 | 0 / 29 | |
| 2.1.2 | 0 / 29 | |
| 2.1.1 | 0 / 29 | |
| 2.1.0 | 0 / 28 | |
| 2.0.43 | 0 / 18 | |
| 2.0.42 | 0 / 19 | |
| 2.0.41 | 0 / 19 | |
| 2.0.37 | 0 / 19 | |
| 2.0.36 | 0 / 19 | |
| 2.0.34 | 0 / 19 |
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.