@modern-js/app-tools MIT 34 versions

@modern-js/app-tools

npm Repository Homepage

A Progressive React Framework for modern web development.

34

Versions

MIT

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

Keywords

reactframeworkmodernmodern.js

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): New deps are all @modern-js/* monorepo siblings pinned to same version; expected for coordinated monorepo releases.	ai	2026/05/27
source-diff	large-new-source-files	AI (source-diff): Large file additions reflect monorepo restructuring across versions; stable pattern for this package.	ai	2026/05/27
dependencies	unvetted-dep:@modern-js/rsbuild-plugin-esbuild	AI (dependencies): Sibling monorepo package released in lockstep; expected pattern for @modern-js/* ecosystem.	ai	2026/05/25
dependencies	unvetted-dep:@modern-js/core	AI (dependencies): Sibling monorepo package released in lockstep; expected pattern for @modern-js/* ecosystem.	ai	2026/05/25
dependencies	unvetted-dep:@modern-js/uni-builder	AI (dependencies): Sibling monorepo package released in lockstep; expected pattern for @modern-js/* ecosystem.	ai	2026/05/25
phantom-deps	phantom-dep:@swc/helpers	AI (phantom-deps): Known implicit runtime dependency; stable for this package.	ai	2026/05/17
phantom-deps	phantom-dep:esbuild-register	AI (phantom-deps): Config-referenced module; stable pattern for build tools.	ai	2026/05/17
bogus-package	bogus-package	AI (bogus-package): Framework homepage with external links; not a phishing indicator given repo and publisher context.	ai	2026/05/17
phantom-deps	phantom-dep:pkg-types	AI (phantom-deps): Config-referenced module; stable pattern for build tools.	ai	2026/05/17
phantom-deps	phantom-dep:mlly	AI (phantom-deps): Config-referenced module; stable pattern for build tools.	ai	2026/05/17

Versions (showing 34 of 34)

Version	Deps	Published
3.2.1	23 / 8	2026-05-21
3.2.0	23 / 8	2026-05-14
3.1.5	23 / 8	2026-04-23
3.1.4	23 / 8	2026-04-15
3.1.3	24 / 8	2026-04-09
3.1.2	24 / 8	2026-04-02
3.1.1	24 / 8	2026-03-26
3.1.0	24 / 8	2026-03-19
3.0.5	23 / 8	2026-03-12
3.0.4	23 / 8	2026-03-04
3.0.3	23 / 8	2026-02-25
3.0.2	23 / 8	2026-02-12
3.0.1	23 / 8	2026-02-05
3.0.0	23 / 8	2026-02-04
2.71.0	28 / 11	2026-05-14
2.70.8	28 / 11	2026-02-26
2.70.7	28 / 11	2026-02-11
2.70.6	28 / 11	2026-02-05
2.70.5	28 / 11	2026-02-04
2.70.4	28 / 11	2026-01-28
2.70.3	28 / 11	2026-01-22
2.70.2	28 / 11	2026-01-14
2.70.1	28 / 11	2026-01-09
2.70.0	28 / 11	2026-01-08
2.69.7	28 / 11	2026-01-04
2.69.6	28 / 11	2025-12-26
2.69.5	28 / 11	2025-12-18
2.69.4	28 / 11	2025-12-10
2.69.3	28 / 11	2025-12-08
2.69.2	28 / 11	2025-12-04
2.69.1	28 / 11	2025-11-25
2.69.0	28 / 11	2025-11-19
2.68.20	28 / 11	2025-11-13
2.68.19	28 / 11	2025-11-06

v3.2.1

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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

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

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

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

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

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

v2.71.0

1 finding

LOW No provenance attestation provenance

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

v2.70.8

1 finding

LOW No provenance attestation provenance

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

v2.70.7

1 finding

LOW No provenance attestation provenance

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

v2.70.6

1 finding

LOW No provenance attestation provenance

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

v2.70.5

1 finding

LOW No provenance attestation provenance

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

v2.70.4

1 finding

LOW No provenance attestation provenance

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

v2.70.3

1 finding

LOW No provenance attestation provenance

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

v2.70.2

1 finding

LOW No provenance attestation provenance

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

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

v2.69.7

1 finding

LOW No provenance attestation provenance

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

v2.69.6

1 finding

LOW No provenance attestation provenance

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

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

v2.69.3

1 finding

LOW No provenance attestation provenance

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

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

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.