@podium/proxy
Transparent http proxy. Dynamically mounts proxy targets on an existing HTTP server instance.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:abslog | AI (dependencies): Known lightweight logging utility; stable dependency of podium-lib packages across many versions. | ai | |
| dependencies | unvetted-dep:@podium/utils | AI (dependencies): Core podium-lib utility package; expected dependency for this ecosystem. | ai | |
| dependencies | unvetted-dep:@metrics/client | AI (dependencies): Metrics client from same maintainer ecosystem; consistent across podium-lib packages. | ai | |
| dependencies | unvetted-dep:@podium/schemas | AI (dependencies): Core podium-lib schema package; expected dependency for this ecosystem. | ai | |
| dependencies | unvetted-dep:@podium/node-http-proxy | AI (dependencies): Podium-lib's own http-proxy fork; expected core dependency for this proxy package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 5.0.37 | 6 / 12 | |
| 5.0.36 | 6 / 12 | |
| 5.0.35 | 6 / 12 | |
| 5.0.34 | 6 / 12 | |
| 5.0.33 | 6 / 12 | |
| 5.0.32 | 6 / 12 | |
| 5.0.31 | 6 / 12 | |
| 5.0.30 | 6 / 12 | |
| 5.0.29 | 6 / 12 | |
| 5.0.28 | 6 / 19 | |
| 5.0.27 | 6 / 19 | |
| 5.0.26 | 6 / 19 | |
| 5.0.25 | 6 / 19 | |
| 5.0.24 | 6 / 19 | |
| 5.0.23 | 6 / 19 | |
| 5.0.22 | 6 / 19 | |
| 5.0.21 | 6 / 19 | |
| 5.0.20 | 6 / 19 | |
| 5.0.19 | 6 / 19 | |
| 5.0.18 | 6 / 19 | |
| 5.0.17 | 6 / 19 | |
| 5.0.16 | 6 / 19 | |
| 5.0.15 | 6 / 16 | |
| 5.0.14 | 6 / 16 | |
| 5.0.13 | 6 / 16 | |
| 5.0.12 | 6 / 16 | |
| 5.0.11 | 6 / 16 | |
| 5.0.10 | 6 / 16 | |
| 5.0.9 | 6 / 16 | |
| 5.0.8 | 6 / 16 | |
| 5.0.7 | 6 / 16 | |
| 5.0.6 | 6 / 16 | |
| 5.0.5 | 6 / 16 | |
| 5.0.4 | 6 / 16 | |
| 5.0.3 | 6 / 16 | |
| 5.0.2 | 6 / 16 | |
| 5.0.1 | 6 / 16 | |
| 5.0.0 | 6 / 16 |
v5.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.