← Home

@vettvangur/vite

npm
5
Versions
Proprietary
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

thorvardurbhelgivettvangurollijonssonmarysomervillesnorriaccrchjayweekendgudjon83hafsig79bgunnarssondevsveinnmarbrynjarthgardarthorsteinsingimarermehtarlimgurgozde

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Proprietary org package; missing description is consistent across versions and not a malware indicator here. ai
bogus-package bogus-package AI (bogus-package): Proprietary internal tooling; sparse metadata is expected for org-internal packages not intended for public discovery. ai
phantom-deps phantom-dep:boxen AI (phantom-deps): Bundled CLI tool; deps may be consumed at runtime via bundled dist rather than direct import. ai
typosquat typosquat.levenshtein:vitest AI (typosquat): Scoped @vettvangur namespace makes typosquat implausible; this is an org-internal Vite wrapper, not impersonating vitest. ai
phantom-deps phantom-dep:vite-plugin-mkcert AI (phantom-deps): Bundled CLI tool; deps may be consumed at runtime via bundled dist rather than direct import. ai
phantom-deps phantom-dep:vite-tsconfig-paths AI (phantom-deps): Bundled CLI tool; deps may be consumed at runtime via bundled dist rather than direct import. ai
phantom-deps phantom-dep:serve-static AI (phantom-deps): Bundled CLI tool; deps may be consumed at runtime via bundled dist rather than direct import. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.82 6 / 10
1.0.81 6 / 10
1.0.80 6 / 10
1.0.79 6 / 10
1.0.28 5 / 9

v1.0.82

1 finding
LOW No provenance attestation provenance

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

v1.0.81

1 finding
LOW No provenance attestation provenance

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

v1.0.80

1 finding
LOW No provenance attestation provenance

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

v1.0.28

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.