@toife/vue MIT 21 versions

@toife/vue

npm

A Frontend framework for Vue

21

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

lamtoi

Keywords

vuetoife frameworkfrontendweb

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
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	2026/04/28
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	2026/04/28
typosquat	typosquat.levenshtein:vite	AI (typosquat): Scoped @toife namespace is a legitimate org; not a typosquat of vite.	ai	2026/04/28
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped @toife namespace is a legitimate org; not a typosquat of yup.	ai	2026/04/28

Versions (showing 21 of 21)

Version	Deps	Published
3.1.6	0 / 14	2026-05-11
3.1.5	0 / 14	2026-05-03
3.1.4	0 / 14	2026-04-26
3.1.3	0 / 14	2026-04-12
3.1.2	0 / 14	2026-04-11
3.0.7	2 / 12	2026-04-02
3.0.6	1 / 13	2026-03-28
3.0.5	1 / 13	2026-03-26
3.0.4	1 / 13	2026-03-22
3.0.3	1 / 13	2026-03-22
3.0.2	1 / 13	2026-03-22
3.0.1	1 / 13	2026-03-22
3.0.0	1 / 14	2026-03-21
2.2.0	0 / 5	2025-11-19
2.1.7	0 / 5	2025-11-14
2.1.6	0 / 5	2025-11-14
2.1.5	0 / 5	2025-11-14
2.1.4	0 / 5	2025-11-13
2.1.3	0 / 5	2025-11-13
2.1.2	0 / 5	2025-11-13
2.1.1	0 / 5	2025-11-13

v3.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.