← Home

@salesforce/plugin-settings

npm Repository Homepage
51
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

forcesalesforcesfdxsalesforcedxsfdx-pluginsf-pluginsf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Salesforce-releases is a high-trust publisher with 1132 approved packages; dormancy likely reflects release cadence changes in the Salesforce CLI ecosystem, not account takeover. ai
maintainer-change maintainer-added AI (maintainer-change): Salesforce org consolidation pattern — individual dev accounts replaced by salesforce-admin; publisher salesforce-releases has strong track record and package has code-signing metadata. ai
maintainer-change maintainer-removed AI (maintainer-change): Mass removal of individual Salesforce developer accounts consistent with org-level consolidation, not a hostile takeover. Package metadata and signing URLs confirm Salesforce ownership. ai
provenance no-provenance AI (provenance): Salesforce uses their own signing infrastructure (sfdx publicKeyUrl/signatureUrl in package.json); lack of Sigstore provenance is expected and stable for this package. ai
dependencies unvetted-dep:fast-levenshtein AI (dependencies): fast-levenshtein is a well-known, widely-used string distance library with no known security issues; its use in a CLI plugin is legitimate and stable. ai

Versions (showing 51 of 163)

View all versions
Version Deps Published
2.4.101 4 / 12
2.4.100 4 / 12
2.4.99 4 / 12
2.4.98 4 / 12
2.4.97 4 / 12
2.4.96 4 / 12
2.4.95 4 / 12
2.4.94 4 / 12
2.4.93 4 / 12
2.4.92 4 / 12
2.4.89 4 / 12
2.4.88 4 / 12
2.4.87 4 / 12
2.4.86 4 / 12
2.4.85 4 / 12
2.4.84 4 / 12
2.4.83 4 / 12
2.4.82 4 / 12
2.4.80 4 / 12
2.4.79 4 / 12
2.4.78 4 / 12
2.4.77 4 / 12
2.4.76 4 / 12
2.4.75 4 / 12
2.4.74 4 / 12
2.4.73 4 / 12
2.4.72 4 / 12
2.4.71 4 / 12
2.4.70 4 / 12
2.4.69 4 / 12
2.4.68 4 / 12
2.4.67 4 / 12
2.4.66 4 / 12
2.4.65 4 / 12
2.4.64 4 / 12
2.4.63 4 / 12
2.4.62 4 / 12
2.4.61 4 / 12
2.4.60 4 / 12
2.4.59 4 / 12
2.4.58 4 / 12
2.4.57 4 / 12
2.4.56 4 / 12
2.4.55 4 / 12
2.4.54 4 / 12
2.4.53 4 / 12
2.4.51 4 / 12
2.4.50 4 / 12
2.4.48 4 / 12
2.4.47 4 / 12
2.4.46 4 / 12

v2.4.101

1 finding
INFO No provenance attestation provenance

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

v2.4.100

1 finding
INFO No provenance attestation provenance

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

v2.4.99

1 finding
INFO No provenance attestation provenance

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

v2.4.98

1 finding
INFO No provenance attestation provenance

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

v2.4.97

1 finding
INFO No provenance attestation provenance

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

v2.4.96

1 finding
INFO No provenance attestation provenance

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

v2.4.95

1 finding
INFO No provenance attestation provenance

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

v2.4.94

1 finding
INFO No provenance attestation provenance

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

v2.4.93

1 finding
INFO No provenance attestation provenance

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

v2.4.92

1 finding
INFO No provenance attestation provenance

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

v2.4.77

1 finding
INFO No provenance attestation provenance

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

v2.4.76

1 finding
INFO No provenance attestation provenance

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

v2.4.73

1 finding
INFO No provenance attestation provenance

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

v2.4.72

1 finding
INFO No provenance attestation provenance

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

v2.4.70

1 finding
INFO No provenance attestation provenance

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

v2.4.69

1 finding
INFO No provenance attestation provenance

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

v2.4.68

1 finding
INFO No provenance attestation provenance

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

v2.4.65

1 finding
INFO No provenance attestation provenance

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

v2.4.64

1 finding
INFO No provenance attestation provenance

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

v2.4.62

1 finding
INFO No provenance attestation provenance

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

v2.4.61

1 finding
INFO No provenance attestation provenance

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

v2.4.60

1 finding
INFO No provenance attestation provenance

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

v2.4.59

1 finding
INFO No provenance attestation provenance

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

v2.4.58

1 finding
INFO No provenance attestation provenance

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

v2.4.56

1 finding
INFO No provenance attestation provenance

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

v2.4.55

1 finding
INFO No provenance attestation provenance

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

v2.4.50

1 finding
INFO No provenance attestation provenance

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

v2.4.48

1 finding
INFO No provenance attestation provenance

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