← Home

vitefu

npm Repository Homepage

Utilities for building frameworks with Vite

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

dominik_gbluwy

Keywords

viteframeworkutilities

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Benign publish-env change on trusted high-trust package; no behavioral risk. ai
provenance no-provenance AI (provenance): Absence of attestation is not a signal by itself for this established package. ai
typosquat typosquat.levenshtein:vite AI (typosquat): vitefu is an intentionally named Vite utility package under the svitejs org, not a typosquat of vite. The name similarity is by design. ai
typosquat typosquat.levenshtein:vitest AI (typosquat): vitefu is a legitimate Vite utilities package; the Levenshtein proximity to vitest is coincidental and not indicative of impersonation. ai

Versions (showing 12 of 12)

Version Deps Published
1.1.3 0 / 4
1.1.2 0 / 4
1.1.1 0 / 4
1.1.0 0 / 4
1.0.7 0 / 4
1.0.6 0 / 4
1.0.5 0 / 4
1.0.4 0 / 4
1.0.3 0 / 4
1.0.2 0 / 4
1.0.1 0 / 4
1.0.0 0 / 4

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bluwy.

LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

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.