@salesforce/core
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib/webOAuthServer.js | AI (source-diff): Inlined i18n message map strings, not obfuscated payloads; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:lib/deviceOauthService.js | AI (source-diff): Inlined i18n message map strings, not obfuscated payloads; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:lib/org/authRemover.js | AI (source-diff): Inlined i18n message map strings, not obfuscated payloads; stable pattern for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 590 versions published; gap reflects major-version branching, not account takeover for this active Salesforce package. | ai | |
| dependencies | unvetted-dep:fast-levenshtein | AI (dependencies): fast-levenshtein is a well-known, benign string distance utility. Its use in @salesforce/core for fuzzy matching is legitimate and poses no security risk. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @salesforce/core is an official Salesforce scoped package with 2955 days of history; Levenshtein match to 'cors' is a false positive. | ai | |
| phantom-deps | phantom-dep:pino-pretty | AI (phantom-deps): pino-pretty is explicitly listed as a direct dependency in package.json; phantom-dep finding is a false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in sfdc.js is used for JWT structure validation (checking 'typ' field); standard JWT handling, not obfuscation. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in messages.js is the documented sfdx-core pattern for loading locale message bundle files; not arbitrary code execution. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex encoding is standard for AES-GCM auth tags and ciphertext in Node.js crypto; this is legitimate cryptographic code in sfdx-core. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 8.31.0 | 19 / 13 | |
| 8.30.4 | 19 / 13 | |
| 8.30.3 | 19 / 13 | |
| 8.30.2 | 19 / 13 | |
| 8.30.1 | 19 / 13 | |
| 8.30.0 | 19 / 13 | |
| 8.29.1 | 19 / 13 | |
| 8.29.0 | 19 / 13 | |
| 8.28.4 | 19 / 13 | |
| 8.28.3 | 19 / 13 | |
| 8.28.2 | 19 / 13 | |
| 8.28.1 | 19 / 13 | |
| 8.28.0 | 19 / 13 | |
| 8.27.1 | 19 / 13 | |
| 8.27.0 | 19 / 13 | |
| 8.26.3 | 19 / 13 | |
| 8.26.2 | 19 / 13 | |
| 8.26.1 | 19 / 13 | |
| 8.26.0 | 19 / 13 | |
| 8.25.1 | 19 / 13 | |
| 8.25.0 | 19 / 13 | |
| 8.24.3 | 19 / 13 | |
| 8.23.7 | 19 / 13 | |
| 8.23.6 | 19 / 13 | |
| 8.23.5 | 19 / 12 | |
| 8.23.4 | 19 / 12 | |
| 8.23.3 | 19 / 12 | |
| 8.23.2 | 19 / 12 | |
| 8.23.1 | 19 / 12 | |
| 8.23.0 | 19 / 12 | |
| 8.22.0 | 19 / 12 | |
| 8.21.3 | 19 / 12 | |
| 8.21.2 | 19 / 12 | |
| 8.21.1 | 19 / 12 | |
| 8.21.0 | 19 / 16 | |
| 8.20.0 | 19 / 16 | |
| 8.19.1 | 19 / 16 | |
| 8.19.0 | 19 / 16 | |
| 8.18.7 | 18 / 16 | |
| 8.18.6 | 18 / 16 | |
| 8.18.5 | 18 / 16 | |
| 8.18.4 | 18 / 16 | |
| 8.18.3 | 18 / 16 | |
| 8.18.2 | 18 / 16 | |
| 8.18.1 | 18 / 16 | |
| 8.18.0 | 18 / 16 | |
| 8.17.0 | 18 / 16 | |
| 8.16.0 | 18 / 16 | |
| 8.15.0 | 18 / 16 | |
| 8.14.1 | 18 / 16 | |
| 8.14.0 | 18 / 16 | |
| 8.13.0 | 18 / 16 | |
| 8.12.0 | 18 / 16 | |
| 8.11.4 | 18 / 16 | |
| 8.11.3 | 18 / 16 | |
| 8.11.2 | 18 / 16 | |
| 8.11.1 | 18 / 16 | |
| 8.11.0 | 18 / 16 | |
| 8.10.3 | 18 / 16 | |
| 8.10.2 | 18 / 16 | |
| 8.10.1 | 18 / 16 | |
| 8.10.0 | 18 / 16 |
v8.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.30.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.30.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.28.4
2 findingsPackage name '@salesforce/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.28.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.27.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.24.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.3
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.2
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.22.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.3
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.2
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.1
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
2 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.1
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
4 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.