← Home

jsforce

npm Repository Homepage
10
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

stomitamshanemcsalesforce-releasesmdonnalley

Keywords

salesforcesalesforce.comsfdcforce.comdatabase.com

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/jsforce-core.js AI (source-diff): Webpack bundle contains standard DH/EC crypto constants; stable false positive for this package. ai
source-diff encoded-string-file:dist/jsforce-core.min.js AI (source-diff): Minified webpack bundle of the same crypto constants. ai
source-diff encoded-string-file:dist/jsforce.js AI (source-diff): Webpack bundle contains standard DH/EC crypto constants; stable false positive. ai
source-diff encoded-string-file:dist/jsforce.min.js AI (source-diff): Minified webpack bundle of the same crypto constants. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used in SFDX registry integration to invoke the sfdx CLI — expected and documented behavior. ai
phantom-deps phantom-dep:@babel/runtime AI (phantom-deps): @babel/runtime is a declared runtime dep used by Babel-transpiled browser output; loaded by convention, not direct import. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding is used for Salesforce Metadata API zip file handling — core library functionality. ai

Versions (showing 10 of 10)

Version Deps Published
3.10.19 15 / 57
3.10.18 15 / 57
3.10.17 15 / 57
3.10.16 16 / 59
3.10.15 16 / 59
3.10.14 16 / 59
3.10.13 16 / 59
3.10.11 16 / 59
3.10.10 16 / 59
3.10.9 16 / 59

v3.10.19

1 finding
LOW No provenance attestation provenance

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

v3.10.18

1 finding
LOW No provenance attestation provenance

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

v3.10.17

1 finding
LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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.