@toife/vue
A Frontend framework for Vue
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@toife/sass-layer | AI (phantom-deps): Same-org style dep used via CSS layers, not direct JS import; stable FP. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same known-maintainer transition. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Provenance data confirms lamtoi is a known maintainer matched by email, not a hijack. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same known-maintainer transition. | ai | |
| phantom-deps | phantom-dep:@toife/gesture | AI (phantom-deps): Same-org scoped dep in a monorepo; not directly imported in this package but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@toife/sass-layer-generator | AI (phantom-deps): Same-org scoped dep in a monorepo; not directly imported in this package but legitimately declared. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @toife namespace is a legitimate org; not a typosquat of yup. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped @toife namespace is a legitimate org; not a typosquat of vite. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.3.3 | 0 / 16 | |
| 3.3.2 | 0 / 16 | |
| 3.3.1 | 0 / 16 | |
| 3.3.0 | 0 / 16 | |
| 3.2.7 | 0 / 16 | |
| 3.2.5 | 3 / 13 | |
| 3.1.6 | 0 / 14 | |
| 3.1.5 | 0 / 14 | |
| 3.1.4 | 0 / 14 | |
| 3.1.3 | 0 / 14 | |
| 3.1.2 | 0 / 14 | |
| 3.0.7 | 2 / 12 | |
| 3.0.6 | 1 / 13 | |
| 3.0.5 | 1 / 13 | |
| 3.0.4 | 1 / 13 | |
| 3.0.3 | 1 / 13 | |
| 3.0.2 | 1 / 13 | |
| 3.0.1 | 1 / 13 | |
| 3.0.0 | 1 / 14 | |
| 2.2.0 | 0 / 5 | |
| 2.1.7 | 0 / 5 | |
| 2.1.6 | 0 / 5 | |
| 2.1.5 | 0 / 5 | |
| 2.1.4 | 0 / 5 | |
| 2.1.3 | 0 / 5 | |
| 2.1.2 | 0 / 5 | |
| 2.1.1 | 0 / 5 |
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
3 findingsAll previous maintainers (toikit) were replaced by new maintainers (lamtoi). This is a strong signal of a potential package hijack and requires careful review.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lamtoi) than the most recent previously approved version (toikit) on 2026-07-12, but lamtoi is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.