← Home

@apimatic/proxy

npm Repository Homepage

provides utilities to route requests through a configurable proxy

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

apimaticdevmehdi991maryamadnan3hamzamahmoodaliasghar1070talhafaheem

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:coverage/lcov-report/prettify.js AI (source-diff): Standard Istanbul/nyc coverage report artifact (Google Code Prettify); not malicious code. ai
source-diff source-size-tripled AI (source-diff): Size increase caused by inclusion of coverage/lcov-report directory, a benign test artifact. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.4 2 / 0
0.1.3 2 / 0
0.1.2 2 / 0
0.1.1 2 / 0

v0.1.3

2 findings
HIGH New obfuscated file: coverage/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.