@jsforce/jsforce-node
Salesforce API Library for JavaScript
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.10.19 | 9 / 57 | |
| 3.10.18 | 9 / 57 | |
| 3.10.17 | 9 / 57 | |
| 3.10.16 | 10 / 59 | |
| 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 | |
| 3.8.0 | 10 / 58 | |
| 3.7.0 | 10 / 58 | |
| 3.6.6 | 10 / 58 | |
| 3.6.5 | 10 / 58 | |
| 3.6.4 | 10 / 58 | |
| 3.6.3 | 10 / 58 | |
| 3.6.2 | 10 / 58 | |
| 3.6.1 | 10 / 58 | |
| 3.6.0 | 10 / 58 | |
| 3.5.2 | 11 / 58 | |
| 3.5.1 | 11 / 58 | |
| 3.5.0 | 11 / 58 | |
| 3.4.2 | 12 / 58 | |
| 3.4.1 | 12 / 58 | |
| 3.4.0 | 12 / 58 | |
| 3.3.4 | 12 / 58 | |
| 3.3.3 | 12 / 58 | |
| 3.3.2 | 12 / 58 | |
| 3.3.1 | 13 / 57 | |
| 3.3.0 | 14 / 58 | |
| 3.2.4 | 14 / 58 | |
| 3.2.3 | 14 / 58 | |
| 3.2.2 | 14 / 58 | |
| 3.2.1 | 14 / 58 | |
| 3.2.0 | 14 / 56 | |
| 3.1.0 | 14 / 56 |
v3.10.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.