@kinem/vue
Vue bindings for kinem
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 @kinem/vue is a Vue bindings package, not a typosquat of vite; edit-distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @kinem/vue is a Vue bindings package, not a typosquat of yup; edit-distance match is coincidental. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 0 / 5 | |
| 0.4.0 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.0 | 0 / 5 |
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.