@salesforce/source-deploy-retrieve No license 45 versions

@salesforce/source-deploy-retrieve

npm Repository Homepage

45

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

ire-npm-team-userjimjagsalesforce-releasesjasonschroeder-sfdcmobifylwc-adminsalesforce-admin

Keywords

SalesforceSalesforceDXmetadatadeployretrieve

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:lib/src/resolve/adapters/webApplicationsSourceAdapter.js	AI (source-diff): Compiled TS with inlined message Map; long lines are build output, not obfuscation.	ai	2026/07/08
maintainer-change	maintainer-added	AI (maintainer-change): Large org roster update by trusted salesforce-releases publisher, no other malicious signal.	ai	2026/07/08
maintainer-change	maintainer-removed	AI (maintainer-change): Bulk maintainer cleanup consistent with org account hygiene, not takeover.	ai	2026/07/08
source-diff	obfuscated-file:lib/src/registry/levenshtein.js	AI (source-diff): TSC-compiled CJS with long inline messages Map; standard build output, not obfuscation.	ai	2026/07/08
dependencies	unvetted-dep:fast-levenshtein	AI (dependencies): fast-levenshtein is a well-known string distance library; its use for metadata type suggestion is legitimate and stable for this package.	ai	2026/04/26
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decoding is expected behavior for this Salesforce metadata API client — the API returns ZIP files as base64 strings that must be decoded. Not a security concern for this package.	ai	2026/04/25
phantom-deps	phantom-dep:@salesforce/types	AI (phantom-deps): First-party Salesforce package in the same org scope; phantom-dep finding is a packaging nuance, not a security risk.	ai	2026/04/25

Versions (showing 45 of 145)

Version	Deps	Published
12.22.5	14 / 17	2025-08-14
12.22.4	14 / 17	2025-08-13
12.22.3	14 / 17	2025-08-12
12.22.2	15 / 17	2025-08-01
12.22.1	15 / 17	2025-07-30
12.22.0	15 / 17	2025-07-25
12.21.6	15 / 17	2025-07-22
12.21.5	15 / 17	2025-07-18
12.21.4	15 / 17	2025-07-15
12.21.3	15 / 17	2025-07-15
12.21.2	15 / 17	2025-07-14
12.21.1	15 / 17	2025-07-09
12.21.0	15 / 17	2025-06-30
12.20.1	15 / 17	2025-06-19
12.20.0	15 / 17	2025-06-17
12.19.10	15 / 17	2025-06-10
12.19.9	15 / 17	2025-06-05
12.19.8	15 / 17	2025-06-02
12.19.7	15 / 17	2025-05-20
12.19.6	15 / 17	2025-05-12
12.19.5	15 / 17	2025-05-05
12.19.4	15 / 17	2025-05-05
12.7.0	13 / 15	2024-09-15
12.5.1	12 / 15	2024-08-20
12.5.0	12 / 15	2024-08-19
12.4.1	12 / 16	2024-08-18
12.4.0	12 / 16	2024-08-15
12.2.1	12 / 16	2024-08-12
12.2.0	12 / 16	2024-08-12
12.1.13	12 / 16	2024-08-11
12.1.12	12 / 16	2024-08-04
12.1.11	12 / 16	2024-08-02
12.1.10	12 / 16	2024-08-01
12.1.9	12 / 16	2024-07-31
12.1.8	12 / 16	2024-07-19
12.1.7	12 / 16	2024-07-17
12.1.6	12 / 16	2024-07-16
12.1.5	12 / 16	2024-07-05
12.1.4	12 / 16	2024-06-28
12.1.3	12 / 16	2024-06-28
12.1.2	12 / 16	2024-06-28
12.1.1	12 / 16	2024-06-28
12.1.0	12 / 16	2024-06-28
12.0.2	12 / 16	2024-06-24
12.0.1	12 / 16	2024-06-20

v12.22.3

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.

v12.22.2

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.

v12.22.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.

v12.21.6

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.

v12.21.5

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.

v12.21.3

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.

v12.21.2

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.

v12.21.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.

v12.21.0

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.

v12.20.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.

v12.20.0

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.

v12.19.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.

v12.19.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.

v12.19.8

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.

v12.19.7

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.

v12.19.5

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.

v12.7.0

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.5.1

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.5.0

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.4.1

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.4.0

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.2.1

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.2.0

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.1.13

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.1.12

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.1.11

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.1.10

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.1.9

2 findings

HIGH New obfuscated file: lib/src/registry/levenshtein.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v12.1.8

1 finding

LOW No provenance attestation provenance

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

v12.1.7

1 finding

LOW No provenance attestation provenance

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

v12.1.6

1 finding

LOW No provenance attestation provenance

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

v12.1.5

1 finding

LOW No provenance attestation provenance

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

v12.1.4

1 finding

LOW No provenance attestation provenance

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

v12.1.3

1 finding

LOW No provenance attestation provenance

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

v12.1.2

1 finding

LOW No provenance attestation provenance

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

v12.1.1

1 finding

LOW No provenance attestation provenance

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

v12.1.0

1 finding

LOW No provenance attestation provenance

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

v12.0.2

1 finding

LOW No provenance attestation provenance

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

v12.0.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.