@midwayjs/faas
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): Established midwayjs monorepo package; v3→v4 major version gap explains dormancy, not a takeover indicator. | ai | |
| dependencies | unvetted-dep:@midwayjs/simple-lock | AI (dependencies): First-party @midwayjs scoped dependency from the same monorepo; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@midwayjs/serverless-http-parser | AI (dependencies): First-party @midwayjs scoped dependency from the same monorepo; stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Midwayjs monorepo does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 3 / 4 | |
| 4.0.3 | 3 / 4 | |
| 4.0.2 | 3 / 4 | |
| 4.0.1 | 3 / 4 | |
| 4.0.0 | 3 / 4 | |
| 3.20.24 | 3 / 5 | |
| 3.20.23 | 3 / 5 | |
| 3.20.22 | 3 / 5 | |
| 3.20.19 | 3 / 5 | |
| 3.20.11 | 3 / 5 | |
| 3.20.10 | 3 / 5 |
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.19
1 finding[Accepted risk] Package 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. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.