@edirect/request
HTTP request utility for eDirect applications. Provides a thin Axios wrapper (`sendRequest`) that automatically resolves service base URLs from the common `config` folder structure, propagates correlation headers (`SessionId`, `QuoteId`), and optionally h
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
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 11.0.58 | 7 / 5 | |
| 11.0.56 | 7 / 5 | |
| 11.0.55 | 7 / 5 | |
| 11.0.54 | 7 / 5 | |
| 11.0.53 | 7 / 5 | |
| 11.0.52 | 7 / 5 | |
| 11.0.49 | 7 / 5 | |
| 11.0.48 | 7 / 5 | |
| 11.0.43 | 7 / 5 | |
| 11.0.41 | 7 / 5 | |
| 11.0.40 | 7 / 5 | |
| 11.0.39 | 7 / 5 | |
| 11.0.37 | 7 / 5 | |
| 11.0.36 | 7 / 5 | |
| 11.0.35 | 7 / 5 | |
| 11.0.34 | 7 / 5 | |
| 11.0.32 | 7 / 5 | |
| 11.0.31 | 7 / 5 | |
| 11.0.29 | 7 / 5 | |
| 11.0.28 | 7 / 5 | |
| 11.0.25 | 7 / 5 |
v11.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.