← Home

arangojs

npm Repository Homepage
7
Versions
—
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

palashkfcelleryaswanthpjeswinthhkernbachapetenchea

Keywords

arangoarangodbaqlnosqlclientdriverapihttprest

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): Hardcoded localhost default (127.0.0.1:8529) for ArangoDB connection; not exfiltration, stable across versions. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires in minified browser bundle (web.js); standard bundler output pattern for this package. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): @types/node is a type-only dep declared for Node.js typings; not a real phantom dep concern. ai

Versions (showing 7 of 7)

Version Deps Published
10.3.1 1 / 0
10.3.0 1 / 0
10.2.2 1 / 0
10.2.1 1 / 0
10.2.0 1 / 0
10.1.2 1 / 0
8.8.1 5 / 0

v10.3.1

1 finding
LOW No provenance attestation provenance

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

v10.3.0

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.

v10.2.2

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.

v10.2.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.

v10.2.0

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.

v10.1.2

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.

v8.8.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.