@midwayjs/grpc
Midway Framework for gRPC
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of provenance is consistent across all Midway versions. | ai |
Versions (showing 51 of 129)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 2 / 2 | |
| 4.0.3 | 2 / 2 | |
| 4.0.2 | 2 / 2 | |
| 4.0.1 | 2 / 2 | |
| 4.0.0 | 2 / 2 | |
| 3.20.24 | 3 / 2 | |
| 3.20.23 | 3 / 2 | |
| 3.20.22 | 3 / 2 | |
| 3.20.19 | 3 / 2 | |
| 3.20.12 | 3 / 2 | |
| 3.20.11 | 3 / 2 | |
| 3.20.6 | 3 / 2 | |
| 3.20.5 | 3 / 2 | |
| 3.20.4 | 3 / 2 | |
| 3.20.3 | 3 / 2 | |
| 3.20.2 | 3 / 2 | |
| 3.20.0 | 3 / 2 | |
| 3.19.3 | 3 / 2 | |
| 3.19.2 | 3 / 2 | |
| 3.19.0 | 3 / 2 | |
| 3.18.2 | 3 / 2 | |
| 3.18.0 | 3 / 2 | |
| 3.17.3 | 3 / 2 | |
| 3.17.1 | 3 / 2 | |
| 3.17.0 | 3 / 2 | |
| 3.16.6 | 3 / 2 | |
| 3.16.5 | 3 / 2 | |
| 3.16.4 | 3 / 2 | |
| 3.16.2 | 3 / 2 | |
| 3.16.0 | 3 / 2 | |
| 3.15.8 | 3 / 2 | |
| 3.15.7 | 3 / 2 | |
| 3.15.6 | 3 / 2 | |
| 3.15.3 | 3 / 2 | |
| 3.15.2 | 3 / 2 | |
| 3.15.0 | 3 / 2 | |
| 3.14.12 | 3 / 2 | |
| 3.14.11 | 3 / 2 | |
| 3.14.7 | 3 / 2 | |
| 3.14.6 | 3 / 2 | |
| 3.14.4 | 3 / 2 | |
| 3.14.3 | 3 / 2 | |
| 3.14.0 | 3 / 2 | |
| 3.13.9 | 3 / 2 | |
| 3.13.8 | 3 / 2 | |
| 3.13.7 | 3 / 2 | |
| 3.13.6 | 3 / 2 | |
| 3.13.5 | 3 / 2 | |
| 3.13.4 | 3 / 2 | |
| 3.13.0 | 3 / 2 | |
| 3.12.10 | 4 / 2 |
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.2
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.3
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.3
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.6
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.7
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.3
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.6
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.4
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.