@modern-js/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @modern-js/core is a legitimate Modern.js framework package, not a typosquat of cors. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package with docs hosted externally; README link dump is expected pattern for this org. | ai | |
| phantom-deps | phantom-dep:@swc/helpers | AI (phantom-deps): @swc/helpers is a known implicit runtime dep for SWC-compiled packages; stable false positive. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 2.71.0 | 4 / 9 | |
| 2.70.8 | 4 / 9 | |
| 2.70.7 | 4 / 9 | |
| 2.70.6 | 4 / 9 | |
| 2.70.5 | 4 / 9 | |
| 2.70.4 | 4 / 9 | |
| 2.70.3 | 4 / 9 | |
| 2.70.2 | 4 / 9 | |
| 2.70.1 | 4 / 9 | |
| 2.70.0 | 4 / 9 | |
| 2.69.7 | 4 / 9 | |
| 2.69.6 | 4 / 9 | |
| 2.69.5 | 4 / 9 | |
| 2.69.4 | 4 / 9 | |
| 2.69.3 | 4 / 9 | |
| 2.69.2 | 4 / 9 | |
| 2.69.1 | 4 / 9 | |
| 2.69.0 | 4 / 9 | |
| 2.68.20 | 4 / 9 | |
| 2.68.19 | 4 / 9 | |
| 2.68.18 | 4 / 9 | |
| 2.68.17 | 4 / 9 | |
| 2.68.16 | 4 / 9 | |
| 2.68.15 | 4 / 9 | |
| 2.68.14 | 4 / 9 | |
| 2.68.13 | 4 / 9 | |
| 2.68.12 | 4 / 9 | |
| 2.68.11 | 4 / 9 | |
| 2.68.10 | 4 / 9 | |
| 2.68.9 | 4 / 9 | |
| 2.68.8 | 4 / 9 | |
| 2.68.7 | 4 / 9 | |
| 2.68.6 | 4 / 9 | |
| 2.68.5 | 4 / 9 | |
| 2.68.4 | 4 / 9 | |
| 2.68.3 | 4 / 9 | |
| 2.68.2 | 4 / 9 | |
| 2.68.1 | 4 / 9 | |
| 2.68.0 | 4 / 9 | |
| 2.67.11 | 4 / 9 | |
| 2.67.10 | 4 / 9 | |
| 2.67.9 | 4 / 9 | |
| 2.67.8 | 4 / 9 | |
| 2.67.7 | 4 / 9 | |
| 2.67.6 | 4 / 9 | |
| 2.67.5 | 4 / 9 |
v2.71.0
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.8
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.7
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.6
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.5
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.4
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.3
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.2
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.1
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.7
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.6
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.5
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.4
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.3
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.2
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.1
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.20
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.19
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.18
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.17
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.16
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.15
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.14
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.13
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.12
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.11
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.10
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.9
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.8
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.7
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.6
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.5
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.4
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.3
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.2
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.1
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.0
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.11
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.10
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.9
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.8
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.7
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.6
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.5
2 findingsPackage name '@modern-js/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.