@midwayjs/core
midway 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@midwayjs/glob | AI (dependencies): Same @midwayjs org scope as this package; stable first-party dependency. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @opentelemetry/api is a well-established CNCF package; not a suspicious addition for a framework core. | ai | |
| provenance | no-provenance | AI (provenance): Long-established MidwayJS package; lack of provenance is consistent across all versions, not a new risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @midwayjs/core is the legitimate Midway framework core, not a typosquat of cors; the name similarity is coincidental. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 4 / 8 | |
| 4.0.3 | 4 / 6 | |
| 4.0.2 | 4 / 6 | |
| 4.0.1 | 4 / 6 | |
| 4.0.0 | 4 / 6 | |
| 3.20.24 | 4 / 6 | |
| 3.20.23 | 4 / 6 | |
| 3.20.22 | 4 / 6 | |
| 3.20.19 | 4 / 6 | |
| 3.20.11 | 4 / 6 |
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.