
Research
Namastex.ai npm Packages Hit with TeamPCP-Style CanisterWorm Malware
Malicious Namastex.ai npm packages appear to replicate TeamPCP-style Canister Worm tradecraft, including exfiltration and self-propagation.
@heroku-cli/plugin-addons
Advanced tools
heroku addons [--all|--app APP]heroku addons:attach ADDON_NAMEheroku addons:create SERVICE:PLANheroku addons:destroy [ADDON]... [flags]heroku addons:detach ATTACHMENT_NAMEheroku addons:docs ADDONheroku addons:downgrade ADDON [PLAN]heroku addons:info ADDONheroku addons:open ADDONheroku addons:plans SERVICEheroku addons:rename ADDON NEW_NAMEheroku addons:servicesheroku addons:upgrade ADDON [PLAN]heroku addons:wait ADDONheroku addons [--all|--app APP]lists your add-ons and attachments
USAGE
$ heroku addons [--all|--app APP]
OPTIONS
-A, --all show add-ons and attachments for all accessible apps
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--json return add-ons in json format
DESCRIPTION
The default filter applied depends on whether you are in a Heroku app
directory. If so, the --app flag is implied. If not, the default of --all
is implied. Explicitly providing either flag overrides the default
behavior.
EXAMPLES
$ heroku addons --all
$ heroku addons --app acme-inc-www
heroku addons:attach ADDON_NAMEattach an existing add-on resource to an app
USAGE
$ heroku addons:attach ADDON_NAME
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--as=as name for add-on attachment
--confirm=confirm overwrite existing add-on attachment with same name
--credential=credential credential name for scoped access to Heroku Postgres
heroku addons:create SERVICE:PLANcreate a new add-on resource
USAGE
$ heroku addons:create SERVICE:PLAN
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
--as=as name for the initial add-on attachment
--confirm=confirm overwrite existing config vars or existing add-on attachments
--name=name name for the add-on resource
--wait watch add-on creation status and exit when complete
heroku addons:destroy [ADDON]... [flags]permanently destroy an add-on resource
USAGE
$ heroku addons:destroy [ADDON]... [flags]
OPTIONS
-a, --app=app app to run command against
-c, --confirm=confirm
-f, --force allow destruction even if connected to other apps
-r, --remote=remote git remote of app to use
heroku addons:detach ATTACHMENT_NAMEdetach an existing add-on resource from an app
USAGE
$ heroku addons:detach ATTACHMENT_NAME
OPTIONS
-a, --app=app (required) app to run command against
-r, --remote=remote git remote of app to use
heroku addons:docs ADDONopen an add-on's Dev Center documentation in your browser
USAGE
$ heroku addons:docs ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--show-url show URL, do not open browser
heroku addons:downgrade ADDON [PLAN]change add-on plan
USAGE
$ heroku addons:downgrade ADDON [PLAN]
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
See available plans with `heroku addons:plans SERVICE`.
Note that `heroku addons:upgrade` and `heroku addons:downgrade` are the same.
Either one can be used to change an add-on plan up or down.
[https://devcenter.heroku.com/articles/managing-add-ons](https://devcenter.heroku.com/articles/managing-add-ons)
EXAMPLE
Upgrade an add-on by service name:
$ heroku addons:upgrade heroku-redis:premium-2
Upgrade a specific add-on:
$ heroku addons:upgrade swimming-briskly-123 heroku-redis:premium-2
heroku addons:info ADDONshow detailed add-on resource and attachment information
USAGE
$ heroku addons:info ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
heroku addons:open ADDONopen an add-on's dashboard in your browser
USAGE
$ heroku addons:open ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--show-url show URL, do not open browser
heroku addons:plans SERVICElist all available plans for an add-on services
USAGE
$ heroku addons:plans SERVICE
OPTIONS
--json output in json format
heroku addons:rename ADDON NEW_NAMErename an add-on
USAGE
$ heroku addons:rename ADDON NEW_NAME
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
heroku addons:serviceslist all available add-on services
USAGE
$ heroku addons:services
OPTIONS
--json output in json format
heroku addons:upgrade ADDON [PLAN]change add-on plan
USAGE
$ heroku addons:upgrade ADDON [PLAN]
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
DESCRIPTION
See available plans with `heroku addons:plans SERVICE`.
Note that `heroku addons:upgrade` and `heroku addons:downgrade` are the same.
Either one can be used to change an add-on plan up or down.
[https://devcenter.heroku.com/articles/managing-add-ons](https://devcenter.heroku.com/articles/managing-add-ons)
EXAMPLE
Upgrade an add-on by service name:
$ heroku addons:upgrade heroku-redis:premium-2
Upgrade a specific add-on:
$ heroku addons:upgrade swimming-briskly-123 heroku-redis:premium-2
heroku addons:wait ADDONshow provisioning status of the add-ons on the app
USAGE
$ heroku addons:wait ADDON
OPTIONS
-a, --app=app app to run command against
-r, --remote=remote git remote of app to use
--wait-interval=wait-interval how frequently to poll in seconds
FAQs
`heroku addons:*` commands
The npm package @heroku-cli/plugin-addons receives a total of 2,569 weekly downloads. As such, @heroku-cli/plugin-addons popularity was classified as popular.
We found that @heroku-cli/plugin-addons demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 24 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.

Research
Malicious Namastex.ai npm packages appear to replicate TeamPCP-style Canister Worm tradecraft, including exfiltration and self-propagation.

Product
Explore exportable charts for vulnerabilities, dependencies, and usage with Reports, Socket’s new extensible reporting framework.

Product
Socket for Jira lets teams turn alerts into Jira tickets with manual creation, automated ticketing rules, and two-way sync.