@modern-js/uni-builder No license 46 versions

@modern-js/uni-builder

npm Repository Homepage

46

Versions

—

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

bytednpmkky_kongjiacongcaohuilin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Fires in compiled third-party bundle (babel-plugin-lodash); stable build artifact pattern for this package.	ai	2026/05/31
semgrep	semgrep:eval-usage	AI (semgrep): eval in compiled postcss-load-config bundle; legitimate config loader pattern, not attacker-controlled.	ai	2026/05/31
bogus-package	bogus-package	AI (bogus-package): Monorepo sub-package; sparse README is expected, not a spam/phishing indicator.	ai	2026/05/31
phantom-deps	phantom-dep:glob	AI (phantom-deps): Declared peer/transitive dep used by convention in this build toolchain.	ai	2026/05/31
phantom-deps	phantom-dep:postcss	AI (phantom-deps): Declared peer/transitive dep used by convention in this build toolchain.	ai	2026/05/31
phantom-deps	phantom-dep:@babel/core	AI (phantom-deps): Framework-scoped package loaded by convention; stable for this package.	ai	2026/05/31
phantom-deps	phantom-dep:@swc/helpers	AI (phantom-deps): Known implicit runtime dep for SWC; stable for this package.	ai	2026/05/31
phantom-deps	phantom-dep:magic-string	AI (phantom-deps): Referenced in config files; stable indirect dep pattern for this package.	ai	2026/05/31
phantom-deps	phantom-dep:es-module-lexer	AI (phantom-deps): Referenced in config files; stable indirect dep pattern for this package.	ai	2026/05/31

Versions (showing 46 of 46)

Version	Deps	Published
2.71.0	57 / 11	2026-05-14
2.70.8	57 / 11	2026-02-26
2.70.7	57 / 11	2026-02-11
2.70.6	57 / 11	2026-02-05
2.70.5	57 / 11	2026-02-04
2.70.4	57 / 11	2026-01-28
2.70.3	57 / 11	2026-01-22
2.70.2	57 / 11	2026-01-14
2.70.1	57 / 11	2026-01-09
2.70.0	57 / 11	2026-01-08
2.69.7	57 / 11	2026-01-04
2.69.6	57 / 11	2025-12-26
2.69.5	57 / 11	2025-12-18
2.69.4	57 / 11	2025-12-10
2.69.3	57 / 11	2025-12-08
2.69.2	57 / 11	2025-12-04
2.69.1	57 / 11	2025-11-25
2.69.0	57 / 11	2025-11-19
2.68.20	57 / 11	2025-11-13
2.68.19	57 / 11	2025-11-06
2.68.18	57 / 11	2025-10-16
2.68.17	57 / 11	2025-10-09
2.68.16	57 / 11	2025-09-26
2.68.15	57 / 11	2025-09-24
2.68.14	57 / 11	2025-09-15
2.68.13	57 / 11	2025-09-15
2.68.12	57 / 11	2025-09-04
2.68.11	57 / 11	2025-08-27
2.68.10	57 / 11	2025-08-21
2.68.9	57 / 11	2025-08-13
2.68.8	57 / 11	2025-08-11
2.68.7	57 / 11	2025-08-06
2.68.6	57 / 11	2025-07-31
2.68.5	57 / 11	2025-07-25
2.68.4	57 / 11	2025-07-23
2.68.3	57 / 11	2025-07-17
2.68.2	57 / 11	2025-07-11
2.68.1	57 / 11	2025-07-10
2.68.0	57 / 11	2025-07-03
2.67.11	57 / 11	2025-06-26
2.67.10	57 / 11	2025-06-18
2.67.9	57 / 11	2025-06-12
2.67.8	57 / 11	2025-06-05
2.67.7	57 / 11	2025-05-28
2.67.6	57 / 11	2025-05-21
2.67.5	57 / 11	2025-05-15

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

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

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

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

v2.70.4

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

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

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

v2.69.4

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

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

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

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

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

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

v2.68.14

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

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

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

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

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

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

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

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

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

v2.68.4

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

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

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

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

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

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

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