@cedarjs/vite No license 27 versions

@cedarjs/vite

npm Repository Homepage

27

Versions

—

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

tobbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:fastify-raw-body	AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:@fastify/url-data	AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:fastify	AI (phantom-deps): fastify is a declared runtime dep used in config/server setup; phantom-dep heuristic false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:@universal-deploy/node	AI (phantom-deps): Declared runtime dep; phantom-dep heuristic false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:fs-extra	AI (phantom-deps): fs-extra referenced in config files; stable false positive for this build/config package.	ai	2026/05/27
phantom-deps	phantom-dep:core-js	AI (phantom-deps): core-js is a common implicit polyfill dependency; not directly imported but legitimately declared.	ai	2026/05/27
provenance	no-provenance	AI (provenance): Large established monorepo package; lack of provenance is common and not a risk signal here.	ai	2026/05/27
dependencies	unvetted-dep:@universal-deploy/node	AI (dependencies): Used for universal deployment support; consistent with framework feature addition.	ai	2026/04/30
dependencies	unvetted-dep:fastify-raw-body	AI (dependencies): Legitimate fastify plugin for raw body parsing; no malware signals.	ai	2026/04/30
dependencies	unvetted-dep:@fastify/url-data	AI (dependencies): Official @fastify scoped plugin; well-known ecosystem package.	ai	2026/04/30
typosquat	typosquat.levenshtein:vitest	AI (typosquat): @cedarjs/vite is a scoped Vite config package for CedarJS, not a typosquat of vitest.	ai	2026/04/28
phantom-deps	phantom-dep:@cedarjs/cookie-jar	AI (phantom-deps): Same org scope; declared runtime dep, phantom-dep heuristic is a false positive here.	ai	2026/04/28
phantom-deps	phantom-dep:rimraf	AI (phantom-deps): rimraf is a declared runtime dep; phantom-dep heuristic fires on config-file references.	ai	2026/04/28
phantom-deps	phantom-dep:cookie	AI (phantom-deps): cookie is a declared runtime dep; phantom-dep heuristic fires on config-file references.	ai	2026/04/28
phantom-deps	phantom-dep:buffer	AI (phantom-deps): buffer is a declared runtime dep; phantom-dep heuristic fires on config-file references.	ai	2026/04/28
phantom-deps	phantom-dep:execa	AI (phantom-deps): execa is a declared runtime dep; phantom-dep heuristic fires on config-file references.	ai	2026/04/28

Versions (showing 27 of 27)

Version	Deps	Published
4.2.0	47 / 16	2026-05-13
4.1.0	42 / 16	2026-04-30
4.0.0	34 / 15	2026-04-12
3.1.1	34 / 15	2026-04-08
3.1.0	34 / 15	2026-03-25
3.0.0	34 / 15	2026-03-23
2.8.1	35 / 15	2026-03-25
2.8.0	35 / 15	2026-03-07
2.7.0	35 / 15	2026-03-03
2.6.0	35 / 15	2026-02-10
2.5.1	35 / 15	2026-02-05
2.5.0	35 / 15	2026-02-02
2.4.1	35 / 15	2026-01-13
2.4.0	35 / 15	2026-01-12
2.3.0	35 / 15	2026-01-02
2.2.1	35 / 15	2025-12-29
2.2.0	36 / 16	2025-12-26
2.1.1	36 / 16	2025-12-19
2.1.0	36 / 16	2025-12-15
2.0.3	36 / 16	2025-12-15
2.0.2	36 / 16	2025-11-30
2.0.1	36 / 16	2025-11-30
2.0.0	36 / 16	2025-11-28
1.1.2	36 / 16	2026-02-08
1.1.1	36 / 16	2025-11-30
1.1.0	36 / 16	2025-11-25
1.0.0	36 / 16	2025-11-17

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.0

1 finding

LOW No provenance attestation provenance

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

v3.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.

v3.1.0

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.8.1

1 finding

LOW No provenance attestation provenance

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

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.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.1

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. 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.

v2.1.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.

v2.0.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.0.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.0.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.

v2.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.

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.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.

v1.1.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.

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.