← Home

@jsforce/jsforce-node

npm Repository Homepage

Salesforce API Library for JavaScript

23
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

salesforce-releases

Keywords

salesforcesalesforce.comsfdcforce.comdatabase.com

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding is used to handle Salesforce Metadata API zip file responses — standard API behavior, not a malicious payload indicator. ai
semgrep semgrep:child-process-import AI (semgrep): child_process is used in sfdx.js to invoke the Salesforce CLI for SFDX registry integration — a documented, legitimate feature of jsforce. ai
dependencies unvetted-dep:faye AI (dependencies): faye is a long-standing dependency used for Salesforce Streaming API (CometD/Bayeux) support — legitimate and expected for this package. ai
dependencies unvetted-dep:multistream AI (dependencies): multistream is used for combining streams in bulk API operations — a standard utility dependency for this package. ai

Versions (showing 23 of 23)

Version Deps Published
3.10.15 10 / 59
3.10.14 10 / 59
3.10.13 10 / 59
3.10.11 10 / 59
3.10.10 10 / 59
3.10.9 10 / 59
3.10.8 10 / 59
3.10.7 10 / 59
3.10.6 10 / 59
3.10.5 10 / 58
3.10.4 10 / 58
3.10.3 10 / 58
3.10.2 10 / 58
3.10.1 10 / 58
3.10.0 10 / 58
3.9.5 10 / 58
3.9.4 10 / 58
3.9.3 10 / 58
3.9.2 10 / 58
3.9.1 10 / 58
3.9.0 10 / 58
3.8.2 10 / 58
3.8.1 10 / 58

v3.10.15

1 finding
LOW No provenance attestation provenance

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

v3.10.14

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.

v3.10.13

1 finding
LOW No provenance attestation provenance

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

v3.10.11

1 finding
LOW No provenance attestation provenance

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

v3.10.10

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.

v3.10.9

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.

v3.9.0

1 finding
LOW No provenance attestation provenance

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

v3.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.