Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@jayree/sfdx-plugin-legacy
Advanced tools
A Salesforce CLI plugin containing all jayree legacy commands.
A Salesforce CLI plugin containing all jayree legacy commands.
sfdx plugins:install @jayree/sfdx-plugin-legacy
sfdx jayree:automation:changeset:deploy
sfdx jayree:automation:changeset:list
sfdx jayree:automation:ltngsync:status
sfdx jayree:packagedescription:create
sfdx jayree:packagedescription:get
sfdx jayree:packagedescription:remove
sfdx jayree:packagedescription:set
sfdx jayree:automation:changeset:deploy
deploy incomming change set to an org (beta)
USAGE
$ sfdx jayree:automation:changeset:deploy [-r <string> -l <string>] [-c] [--nodialog -s <string>] [-u <string>] [--apiversion
<string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-c, --checkonly validate deploy but don’t save to
the org (default:false)
-l, --testlevel=<option> deployment testing level
(Default,RunSpecifiedTests,RunLocalT
ests,RunAllTestsInOrg)
<options: Default|RunSpecifiedTests|
RunLocalTests|RunAllTestsInOrg>
-r, --runtests=<value> tests to run if --testlevel
RunSpecifiedTests
-s, --changeset=<value> name of changeset to deploy
-u, --targetusername=<value> username or alias for the target
org; overrides default target org
--apiversion=<value> override the api version used for
api requests made by this command
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
--nodialog don't show the dialog wizard
DESCRIPTION
deploy incomming change set to an org (beta)
EXAMPLES
$ sfdx jayree:automation:changeset:deploy -s ChangeSet -l RunLocalTests --nodialog
Deploying Change Set 'ChangeSet'...
=== Status
Status: Pending
jobid: 0Xxx100000xx1x1
$ sfdx jayree:automation:changeset:deploy
? Change Sets Awaiting Deployment (Use arrow keys)
ChangeSet3
ChangeSet2
❯ ChangeSet1
See code: src/commands/jayree/automation/changeset/deploy.ts
sfdx jayree:automation:changeset:list
list incomming change sets of an org (beta)
USAGE
$ sfdx jayree:automation:changeset:list [-u <string>] [--apiversion <string>] [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-u, --targetusername=<value> username or alias for the target
org; overrides default target org
--apiversion=<value> override the api version used for
api requests made by this command
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
list incomming change sets of an org (beta)
See code: src/commands/jayree/automation/changeset/list.ts
sfdx jayree:automation:ltngsync:status
check the Lightning Sync User Sync Status and reset sync if needed (beta)
USAGE
$ sfdx jayree:automation:ltngsync:status -o <string> [-s] [-w <integer>] [-u <string>] [--apiversion <string>] [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-o, --officeuser=<value> (required) 'name' (firstname
lastname) of the SF user
-s, --statusonly get Lightning Sync status of the SF
user, only
-u, --targetusername=<value> username or alias for the target
org; overrides default target org
-w, --wait=<value> wait time for command to wait for
status change in minutes (default:
infinitely)
--apiversion=<value> override the api version used for
api requests made by this command
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
check the Lightning Sync User Sync Status and reset sync if needed (beta)
EXAMPLES
$ sfdx jayree:automation:ltngsync:status -o 'Name'
configSetup: User assigned to active Lightning Sync configuration... Yes
userContacts/userEvents: Salesforce and Exchange email addresses linked... Linked/Linked
userContacts/userEvents: Salesforce to Exchange sync status... Initial sync completed/Initial sync completed
userContacts/userEvents: Exchange to Salesforce sync status... Initial sync completed/Initial sync completed
See code: src/commands/jayree/automation/ltngsync/status.ts
sfdx jayree:packagedescription:create
creates an empty package with the description
USAGE
$ sfdx jayree:packagedescription:create (-d <string> -f <string>) [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-d, --description=<value> (required) new description value
-f, --file=<value> (required) file to create
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
creates an empty package with the description
EXAMPLES
$ sfdx jayree:packagedescription:create --file FILENAME --description 'DESCRIPTION'
See code: src/commands/jayree/packagedescription/create.ts
sfdx jayree:packagedescription:get
get the description within a package
USAGE
$ sfdx jayree:packagedescription:get -f <string> [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-f, --file=<value> (required) file to read
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
get the description within a package
EXAMPLES
$ sfdx jayree:packagedescription:get --file FILENAME
Description of Package FILENAME
See code: src/commands/jayree/packagedescription/get.ts
sfdx jayree:packagedescription:remove
remove the description within a package
USAGE
$ sfdx jayree:packagedescription:remove -f <string> [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-f, --file=<value> (required) file to read
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
remove the description within a package
EXAMPLES
$ sfdx jayree:packagedescription:remove --file FILENAME
See code: src/commands/jayree/packagedescription/remove.ts
sfdx jayree:packagedescription:set
set the description within a package
USAGE
$ sfdx jayree:packagedescription:set (-d <string> -f <string>) [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-d, --description=<value> (required) new description value
-f, --file=<value> (required) file to read
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
set the description within a package
EXAMPLES
$ sfdx jayree:packagedescription:set --file FILENAME --description 'NEW DESCRIPTION'
FAQs
A Salesforce CLI plugin containing all jayree legacy commands.
The npm package @jayree/sfdx-plugin-legacy receives a total of 0 weekly downloads. As such, @jayree/sfdx-plugin-legacy popularity was classified as not popular.
We found that @jayree/sfdx-plugin-legacy demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.