@modern-js/utils
A Progressive React Framework for modern web development.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 4478 versions in registry from an active monorepo; apparent dormancy gaps are artifacts of version selection, not true inactivity. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lodash-es and import-meta-resolve are well-known legitimate packages; lodash-es is the ESM companion to the existing lodash dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package from Modern.js framework; sparse per-package READMEs are typical for this org and not indicative of spam or malicious intent. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dependency for SWC-compiled packages; not a real phantom dep issue for this package. | ai | |
| dependencies | unvetted-dep:rslog | AI (dependencies): rslog is a logging package from the same ByteDance/web-infra-dev ecosystem as Modern.js; it is a stable, intentional dependency across all versions of this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 6 / 7 | |
| 3.2.0 | 6 / 7 | |
| 3.1.5 | 6 / 7 | |
| 3.1.4 | 6 / 7 | |
| 3.1.3 | 6 / 7 | |
| 3.1.2 | 6 / 7 | |
| 3.1.1 | 6 / 7 | |
| 3.1.0 | 6 / 7 | |
| 3.0.5 | 6 / 7 | |
| 3.0.4 | 6 / 7 | |
| 3.0.3 | 6 / 7 | |
| 3.0.2 | 6 / 7 | |
| 3.0.1 | 6 / 7 | |
| 3.0.0 | 6 / 7 | |
| 2.71.0 | 4 / 8 | |
| 2.70.8 | 4 / 8 | |
| 2.70.7 | 4 / 8 | |
| 2.70.6 | 4 / 8 | |
| 2.70.5 | 4 / 8 | |
| 2.70.4 | 4 / 8 | |
| 2.70.3 | 4 / 8 | |
| 2.70.2 | 4 / 8 | |
| 2.70.1 | 4 / 8 | |
| 2.70.0 | 4 / 8 | |
| 2.69.7 | 4 / 8 | |
| 2.69.6 | 4 / 8 | |
| 2.69.5 | 4 / 8 | |
| 2.69.4 | 4 / 8 | |
| 2.69.3 | 4 / 8 | |
| 2.69.2 | 4 / 8 | |
| 2.69.1 | 4 / 8 | |
| 2.69.0 | 4 / 8 | |
| 2.68.20 | 4 / 8 | |
| 2.68.19 | 4 / 8 | |
| 2.68.2 | 4 / 8 |
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.68.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.68.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.68.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.