@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 3 / 4 | |
| 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 | |
| 3.20.4 | 3 / 5 | |
| 3.20.3 | 3 / 5 | |
| 3.20.0 | 3 / 5 | |
| 3.19.2 | 3 / 5 | |
| 3.19.0 | 3 / 5 | |
| 3.18.2 | 3 / 5 | |
| 3.18.0 | 3 / 5 | |
| 3.17.1 | 3 / 5 | |
| 3.17.0 | 3 / 5 | |
| 3.16.5 | 3 / 5 | |
| 3.16.4 | 3 / 5 | |
| 3.16.2 | 3 / 5 | |
| 3.16.0 | 3 / 5 | |
| 3.15.8 | 3 / 5 | |
| 3.15.6 | 3 / 5 | |
| 3.15.2 | 3 / 5 | |
| 3.15.0 | 3 / 5 | |
| 3.14.12 | 3 / 5 | |
| 3.14.11 | 3 / 5 | |
| 3.14.7 | 3 / 5 | |
| 3.14.4 | 3 / 5 | |
| 3.14.3 | 3 / 5 | |
| 3.14.0 | 3 / 5 | |
| 3.13.9 | 3 / 5 | |
| 3.13.8 | 3 / 5 | |
| 3.13.7 | 3 / 5 | |
| 3.13.6 | 3 / 5 | |
| 3.13.5 | 3 / 5 | |
| 3.13.0 | 3 / 5 | |
| 3.12.10 | 4 / 4 | |
| 3.12.8 | 4 / 4 | |
| 3.12.5 | 4 / 4 | |
| 3.12.3 | 5 / 4 | |
| 3.12.2 | 5 / 4 | |
| 3.12.1 | 5 / 4 | |
| 3.12.0 | 5 / 4 | |
| 3.11.15 | 5 / 4 | |
| 3.11.12 | 5 / 4 | |
| 3.11.11 | 5 / 4 |
v3.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.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.15.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.