@descope/vue-sdk
The Descope Vue SDK provides convenient access to the Descope for an application written on top of Vue. You can read more on the [Descope Website](https://descope.com).
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
Versions (showing 11 of 211)
| Version | Deps | Published |
|---|---|---|
| 2.0.25 | 8 / 39 | |
| 2.0.24 | 8 / 39 | |
| 2.0.23 | 8 / 39 | |
| 2.0.22 | 8 / 39 | |
| 2.0.21 | 8 / 39 | |
| 2.0.20 | 8 / 39 | |
| 2.0.19 | 7 / 38 | |
| 2.0.17 | 7 / 38 | |
| 2.0.16 | 7 / 38 | |
| 2.0.15 | 7 / 38 | |
| 2.0.14 | 7 / 38 |
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.