← Home

@lark-apaas/fullstack-rspack-preset

npm

> 开箱即用的 Fullstack Rspack 配置预设

23
Versions
MIT
License
Yes
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_bytechengshihao1yanmingjiangprgrmr_byte

Keywords

fullstackrspackpresets

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): New maintainer fengtianran_byted is within the same ByteDance org; consistent with internal team expansion. ai
publish-pattern new-deps-added AI (publish-pattern): @swc/plugin-styled-jsx is a legitimate SWC ecosystem plugin; no malicious indicators. ai
phantom-deps phantom-dep:react-refresh AI (phantom-deps): Referenced in rspack config files by convention, not direct import; stable false positive. ai
phantom-deps phantom-dep:postcss-import AI (phantom-deps): Referenced in config files by convention; stable false positive for this build-preset package. ai
phantom-deps phantom-dep:@swc/plugin-styled-jsx AI (phantom-deps): Referenced in config files by convention; stable false positive for this build-preset package. ai
install-scripts install-script:postinstall AI (install-scripts): Postinstall runs patch-package apply-patch pattern; stable and documented for this package. ai
phantom-deps phantom-dep:@babel/parser AI (phantom-deps): Framework-scoped babel package loaded by convention; stable false positive. ai
phantom-deps phantom-dep:@babel/traverse AI (phantom-deps): Framework-scoped babel package loaded by convention; stable false positive. ai
phantom-deps phantom-dep:@babel/types AI (phantom-deps): Framework-scoped babel package loaded by convention; stable false positive. ai
phantom-deps phantom-dep:patch-package AI (phantom-deps): patch-package is invoked via npm script, not imported directly; false positive for this package. ai

Versions (showing 23 of 23)

Version Deps Published
1.0.53 22 / 4
1.0.52 22 / 4
1.0.51 22 / 4
1.0.36 19 / 4
1.0.35 19 / 4
1.0.28 17 / 4
1.0.20 17 / 4
1.0.19 17 / 4
1.0.12 16 / 4
1.0.11 15 / 4
1.0.10 14 / 5
1.0.9 14 / 5
1.0.8 14 / 5
1.0.7 14 / 5
1.0.6 14 / 5
1.0.5 14 / 5
1.0.4 14 / 5
1.0.3 14 / 5
1.0.2 13 / 5
1.0.1 13 / 5
1.0.0 13 / 5
0.1.1 6 / 5
0.1.0 6 / 5

v1.0.52

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

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

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yanmingjiang → duanlikang_byte (on 2026-01-29, known maintainer) provenance

This version was published by a different npm account (duanlikang_byte) than the most recent previously approved version (yanmingjiang) on 2026-01-29, but duanlikang_byte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.35

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yanmingjiang → duanlikang_byte (on 2026-01-27, known maintainer) provenance

This version was published by a different npm account (duanlikang_byte) than the most recent previously approved version (yanmingjiang) on 2026-01-27, but duanlikang_byte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.28

2 findings
HIGH Publisher changed: yanmingjiang → byted.lycoiref (on 2026-01-07) provenance

This version was published by a different npm account than previous versions on 2026-01-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.20

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yanmingjiang → xiaochuanzhang_byted (on 2025-12-09, known maintainer) provenance

This version was published by a different npm account (xiaochuanzhang_byted) than the most recent previously approved version (yanmingjiang) on 2025-12-09, but xiaochuanzhang_byted is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.19

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yanmingjiang → xiaochuanzhang_byted (on 2025-12-09, known maintainer) provenance

This version was published by a different npm account (xiaochuanzhang_byted) than the most recent previously approved version (yanmingjiang) on 2025-12-09, but xiaochuanzhang_byted is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.12

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: npm run apply-patch

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

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yanmingjiang → duanlikang_byte (on 2025-11-14, known maintainer) provenance

This version was published by a different npm account (duanlikang_byte) than the most recent previously approved version (yanmingjiang) on 2025-11-14, but duanlikang_byte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.8

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: yanmingjiang → duanlikang_byte (on 2025-11-06, known maintainer) provenance

This version was published by a different npm account (duanlikang_byte) than the most recent previously approved version (yanmingjiang) on 2025-11-06, but duanlikang_byte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: duanlikang_byte → yanmingjiang (on 2025-11-06, known maintainer) provenance

This version was published by a different npm account (yanmingjiang) than the most recent previously approved version (duanlikang_byte) on 2025-11-06, but yanmingjiang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: duanlikang_byte → yanmingjiang (on 2025-11-06, known maintainer) provenance

This version was published by a different npm account (yanmingjiang) than the most recent previously approved version (duanlikang_byte) on 2025-11-06, but yanmingjiang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.0.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: duanlikang_byte → yanmingjiang (on 2025-11-05, known maintainer) provenance

This version was published by a different npm account (yanmingjiang) than the most recent previously approved version (duanlikang_byte) on 2025-11-05, but yanmingjiang is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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

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

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