Package Health Score

53 / 100

security
Security review needed
popularity
Small
maintenance
Inactive
community
Active

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
8.1.7	\|	06/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
8.0.6	\|	04/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
7.68.0	\|	02/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
7.62.0	\|	08/2022	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.9.12	\|	05/2018		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

ISC

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Small

Weekly Downloads (4,381)

GitHub Stars: 851
Forks: 211
Contributors: 140

Direct Usage Popularity

The npm package @heroku-cli/plugin-ci receives a total of 4,381 downloads a week. As such, we scored @heroku-cli/plugin-ci popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @heroku-cli/plugin-ci, we found that it has been starred 851 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: No
Contributors: 140
Funding: No

A good and healthy external contribution signal for @heroku-cli/plugin-ci project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like @heroku-cli/plugin-ci is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

Open Issues: 178
Open PR: 21
Last Release: 11 months ago
Last Commit: 23 days ago

Further analysis of the maintenance status of @heroku-cli/plugin-ci based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that @heroku-cli/plugin-ci demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=14

Age: 6 years
Dependencies: 16 Direct
Versions: 80
Install Size: 49.2 kB
Dist-tags: 2
# of Files: 26
Maintainers: 51
TS Typings: No

@heroku-cli/plugin-ci has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

@heroku-cli/plugin-ci

Heroku CLI plugin for Heroku CI

Usage

$ npm install -g @heroku-cli/plugin-ci
$ heroku COMMAND
running command...
$ heroku (--version|-v)
@heroku-cli/plugin-ci/8.1.7 darwin-x64 node-v16.19.0
$ heroku --help [COMMAND]
USAGE
  $ heroku COMMAND
...

Commands

`heroku ci`

display the most recent CI runs for the given pipeline

USAGE
  $ heroku ci [-a ] [--watch] [-p ] [--json]

FLAGS
  -a, --app=       app name
  -p, --pipeline=  name of pipeline
  --json                  output in json format
  --watch                 keep running and watch for new and update tests

DESCRIPTION
  display the most recent CI runs for the given pipeline

EXAMPLES
  $ heroku ci --app murmuring-headland-14719

See code: src/commands/ci/index.ts

`heroku ci:info TEST-RUN`

show the status of a specific test run

USAGE
  $ heroku ci:info TEST-RUN [-a ] [--node ] [-p ]

FLAGS
  -a, --app=       app name
  -p, --pipeline=  name of pipeline
  --node=          the node number to show its setup and output

DESCRIPTION
  show the status of a specific test run

EXAMPLES
  $ heroku ci:info 1288 --app murmuring-headland-14719

See code: src/commands/ci/info.ts

`heroku ci:last`

looks for the most recent run and returns the output of that run

USAGE
  $ heroku ci:last [-a ] [--node ] [-p ]

FLAGS
  -a, --app=       app name
  -p, --pipeline=  name of pipeline
  --node=          the node number to show its setup and output

DESCRIPTION
  looks for the most recent run and returns the output of that run

EXAMPLES
  $ heroku ci:last --pipeline=my-pipeline --node 100

See code: src/commands/ci/last.ts

`heroku ci:rerun [NUMBER]`

rerun tests against current directory

USAGE
  $ heroku ci:rerun [NUMBER] [-a ] [-p ]

FLAGS
  -a, --app=       app name
  -p, --pipeline=  name of pipeline

DESCRIPTION
  rerun tests against current directory

EXAMPLES
  $ heroku ci:rerun 985 --app murmuring-headland-14719

See code: src/commands/ci/rerun.ts

`heroku ci:run`

run tests against current directory

USAGE
  $ heroku ci:run [-a ] [-p ]

FLAGS
  -a, --app=       app name
  -p, --pipeline=  name of pipeline

DESCRIPTION
  run tests against current directory

EXAMPLES
  $ heroku ci:run --app murmuring-headland-14719

See code: src/commands/ci/run.ts

`heroku ci:info`

Shows the information for a particular ci run on a pipeline.

USAGE
  $ heroku ci:info 555 --pipeline=my-pipeline # 555 is the test number

`heroku ci:last`

Shows the information for the last run for a given pipeline.

USAGE
  $ heroku ci:last --pipeline=my-pipeline

`heroku ci:run`

Run this from within your repo directory to trigger a test agains the current branch and commit.

USAGE
  $ heroku ci:run --pipeline=my-pipeline

`heroku ci:rerun`

Re-run a previous test run. If no test run number is provided, the most recent test run will be re-run.

USAGE
  $ heroku ci:rerun 555 --pipeline=my-pipeline  # 555 is the test number

@heroku-cli/plugin-ci dependencies

@heroku-cli/color @heroku-cli/command @oclif/core ansi-escapes async-file debug fs-extra github-url-to-object got inquirer phoenix tmp tslib uuid validator ws

@heroku-cli/plugin-ci development dependencies

@fancy-test/nock @heroku-cli/schema @oclif/test @types/chai @types/inquirer @types/mocha @types/nock @types/phoenix @types/uuid @types/validator @types/ws chai globby mocha nock nyc oclif ts-node typescript

FAQs

What is @heroku-cli/plugin-ci?

Heroku CLI plugin for Heroku CI. Visit Snyk Advisor to see a full health score report for @heroku-cli/plugin-ci, including popularity, security, maintenance & community analysis.

Is @heroku-cli/plugin-ci popular?

The npm package @heroku-cli/plugin-ci receives a total of 4,381 weekly downloads. As such, @heroku-cli/plugin-ci popularity was classified as small. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @heroku-cli/plugin-ci well maintained?

We found indications that @heroku-cli/plugin-ci is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @heroku-cli/plugin-ci safe to use?

While scanning the latest version of @heroku-cli/plugin-ci, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 18 April-2024, at 23:20 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (4,381)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

@heroku-cli/plugin-ci

Usage

Commands

heroku ci

heroku ci:info TEST-RUN

heroku ci:last

heroku ci:rerun [NUMBER]

heroku ci:run

heroku ci:info

heroku ci:last

heroku ci:run

heroku ci:rerun

@heroku-cli/plugin-ci dependencies

@heroku-cli/plugin-ci development dependencies

FAQs

What is @heroku-cli/plugin-ci?

Is @heroku-cli/plugin-ci popular?

Is @heroku-cli/plugin-ci well maintained?

Is @heroku-cli/plugin-ci safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues

`heroku ci`

`heroku ci:info TEST-RUN`

`heroku ci:last`

`heroku ci:rerun [NUMBER]`

`heroku ci:run`

`heroku ci:info`

`heroku ci:last`

`heroku ci:run`

`heroku ci:rerun`