@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, 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 |
|---|---|---|---|---|
| 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 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 8.2.9 | 18 / 11 | |
| 8.2.8 | 18 / 11 | |
| 8.2.7 | 18 / 11 | |
| 8.2.6 | 18 / 11 | |
| 8.2.5 | 18 / 11 | |
| 8.2.4 | 18 / 11 | |
| 8.2.3 | 18 / 11 | |
| 8.2.2 | 18 / 11 | |
| 8.2.1 | 18 / 11 | |
| 8.2.0 | 18 / 11 | |
| 8.1.3 | 18 / 11 | |
| 8.1.2 | 18 / 11 | |
| 8.1.1 | 18 / 11 | |
| 8.1.0 | 18 / 11 | |
| 8.0.5 | 18 / 11 | |
| 8.0.4 | 18 / 11 | |
| 8.0.3 | 18 / 11 | |
| 8.0.2 | 18 / 13 | |
| 8.0.1 | 18 / 13 |
v8.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.