@gravity-ui/gateway
A flexible and powerful Express controller for working with REST and gRPC APIs in Node.js applications.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used in a CLI bin script for applying patches; expected and documented behavior for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established gravity-ui org package with 72 versions; sparse README is a style choice, not a spam indicator. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.14.0 | 9 / 25 | |
| 4.13.0 | 9 / 25 | |
| 4.12.1 | 9 / 25 | |
| 4.12.0 | 9 / 25 | |
| 4.11.1 | 9 / 25 | |
| 4.11.0 | 9 / 25 | |
| 4.10.4 | 9 / 25 | |
| 4.10.3 | 9 / 25 | |
| 4.10.2 | 9 / 25 | |
| 4.10.1 | 9 / 25 | |
| 4.10.0 | 9 / 25 | |
| 4.9.0 | 9 / 25 | |
| 4.8.0 | 9 / 25 | |
| 4.7.2 | 9 / 25 | |
| 4.7.1 | 9 / 25 | |
| 4.7.0 | 9 / 25 | |
| 4.6.0 | 9 / 25 | |
| 4.5.0 | 9 / 25 | |
| 4.4.0 | 9 / 25 | |
| 4.3.0 | 9 / 25 | |
| 4.2.1 | 9 / 25 | |
| 4.2.0 | 9 / 25 | |
| 4.1.0 | 9 / 25 | |
| 4.0.0 | 9 / 25 | |
| 3.2.4 | 9 / 24 | |
| 3.2.3 | 9 / 24 | |
| 3.2.2 | 9 / 24 |
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.