@ssgoi/vue
Vue bindings for SSGOI - Native app-like page transitions for Vue applications
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @ssgoi/vue; Levenshtein match to 'vite' is incidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @ssgoi/vue; Levenshtein match to 'yup' is incidental, not impersonation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.4.0 | 1 / 13 | |
| 6.3.0 | 1 / 13 | |
| 6.2.0 | 1 / 13 | |
| 6.1.0 | 1 / 13 | |
| 6.0.0 | 1 / 13 | |
| 5.2.0 | 1 / 13 | |
| 5.0.0 | 1 / 13 | |
| 4.0.0 | 1 / 13 | |
| 3.1.0 | 1 / 13 | |
| 3.0.0 | 1 / 13 | |
| 2.5.2 | 1 / 13 |
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.