@lark-apaas/fullstack-vite-preset MIT 24 versions

@lark-apaas/fullstack-vite-preset

npm

Vite preset for Fullstack applications, providing a complete replacement for `@lark-apaas/fullstack-rspack-preset`.

24

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

bytednpmfengtianran_bytedxiaochuanzhang_bytedbyted.lycoirefduanlikang_byte

Keywords

fullstackvitepresets

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): Added deps are well-known ecosystem packages matching the package's vite-preset purpose.	ai	2026/05/29
phantom-deps	phantom-dep:@lark-apaas/miaoda-inspector-jsx-runtime	AI (phantom-deps): Same-org dep used via config/preset wiring, not direct import — stable false positive for this package.	ai	2026/05/26
phantom-deps	phantom-dep:@babel/parser	AI (phantom-deps): Framework-scoped babel package loaded by convention; stable false positive.	ai	2026/05/21
phantom-deps	phantom-dep:postcss-import	AI (phantom-deps): Referenced in config files by convention; stable false positive for this Vite preset package.	ai	2026/05/21
phantom-deps	phantom-dep:styled-jsx	AI (phantom-deps): Referenced in config files by convention; stable false positive for this Vite preset package.	ai	2026/05/21
phantom-deps	phantom-dep:@lark-apaas/styled-jsx	AI (phantom-deps): Same org scope; loaded indirectly by convention; stable false positive.	ai	2026/05/21
phantom-deps	phantom-dep:@babel/traverse	AI (phantom-deps): Framework-scoped babel package loaded by convention; stable false positive.	ai	2026/05/21
phantom-deps	phantom-dep:@babel/types	AI (phantom-deps): Framework-scoped babel package loaded by convention; stable false positive.	ai	2026/05/21

Versions (showing 24 of 24)

Version	Deps	Published
1.0.24	21 / 4	2026-06-04
1.0.23	21 / 4	2026-06-02
1.0.22	21 / 4	2026-05-21
1.0.21	21 / 4	2026-05-08
1.0.20	21 / 4	2026-04-28
1.0.19	21 / 4	2026-04-27
1.0.18	21 / 4	2026-04-23
1.0.17	21 / 4	2026-04-22
1.0.16	21 / 4	2026-04-21
1.0.15	21 / 4	2026-04-17
1.0.14	21 / 4	2026-03-26
1.0.13	21 / 4	2026-03-12
1.0.12	21 / 4	2026-03-11
1.0.11	21 / 4	2026-03-10
1.0.10	21 / 4	2026-03-10
1.0.9	20 / 4	2026-03-06
1.0.8	17 / 4	2026-03-03
1.0.7	18 / 4	2026-02-26
1.0.6	18 / 4	2026-02-13
1.0.5	18 / 4	2026-02-11
1.0.4	18 / 4	2026-02-09
1.0.3	15 / 4	2026-02-05
1.0.2	15 / 4	2026-02-04
1.0.1	15 / 4	2026-02-03

v1.0.24

1 finding

LOW No provenance attestation provenance

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

v1.0.23

1 finding

LOW No provenance attestation provenance

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

v1.0.22

1 finding

LOW No provenance attestation provenance

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

v1.0.21

1 finding

LOW No provenance attestation provenance

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

v1.0.19

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

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

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

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

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

1 finding

LOW No provenance attestation provenance

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

v1.0.13

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

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

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

v1.0.6

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

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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