@modern-js/server-core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@web-std/fetch | AI (dependencies): @web-std/fetch is a legitimate web standards fetch polyfill; stable dependency for this server framework package. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): Known implicit runtime dep for SWC-compiled output; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@web-std/file | AI (phantom-deps): Config-referenced transitive dep in monorepo build; not a real phantom. | ai | |
| phantom-deps | phantom-dep:@web-std/fetch | AI (phantom-deps): Config-referenced transitive dep in monorepo build; not a real phantom. | ai | |
| phantom-deps | phantom-dep:@web-std/stream | AI (phantom-deps): Config-referenced transitive dep in monorepo build; not a real phantom. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package README is intentionally minimal; not spam. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 11 / 9 | |
| 3.2.0 | 11 / 9 | |
| 3.1.5 | 11 / 9 | |
| 3.1.4 | 11 / 9 | |
| 3.1.3 | 11 / 9 | |
| 3.1.2 | 11 / 9 | |
| 3.1.1 | 11 / 9 | |
| 3.1.0 | 11 / 9 | |
| 3.0.5 | 11 / 9 | |
| 3.0.4 | 11 / 9 | |
| 3.0.3 | 11 / 9 | |
| 3.0.2 | 11 / 9 | |
| 3.0.1 | 11 / 9 | |
| 3.0.0 | 11 / 9 | |
| 2.71.0 | 12 / 11 | |
| 2.70.8 | 12 / 11 | |
| 2.70.7 | 12 / 11 | |
| 2.70.6 | 12 / 11 | |
| 2.70.5 | 12 / 11 | |
| 2.70.4 | 12 / 11 | |
| 2.70.3 | 12 / 11 | |
| 2.70.2 | 12 / 11 | |
| 2.70.1 | 12 / 11 | |
| 2.70.0 | 12 / 11 | |
| 2.69.7 | 12 / 11 | |
| 2.69.6 | 12 / 11 | |
| 2.69.5 | 12 / 11 | |
| 2.69.4 | 12 / 11 | |
| 2.69.3 | 12 / 11 | |
| 2.69.2 | 12 / 11 | |
| 2.69.1 | 12 / 11 | |
| 2.69.0 | 12 / 11 | |
| 2.68.20 | 12 / 11 | |
| 2.68.19 | 12 / 11 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.