Package Health Score

50 / 100

security
Security review needed
popularity
Popular
maintenance
Inactive
community
Sustainable

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
1.26.10	\|	12/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.25.1	\|	12/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.3.16	\|	02/2018		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

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

Popular

Weekly Downloads (109,519)

GitHub Stars: 61
Forks: 55
Contributors: 30

Direct Usage Popularity

The npm package @oclif/dev-cli receives a total of 109,519 downloads a week. As such, we scored @oclif/dev-cli popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @oclif/dev-cli, we found that it has been starred 61 times.

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

Community

Sustainable

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

With more than 10 contributors for the @oclif/dev-cli repository, this is possibly a sign for a growing and inviting community.

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

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

No Recent Commits

Open Issues: 50
Open PR: 31
Last Release: 3 years ago
Last Commit: 3 years ago

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

An important project maintenance signal to consider for @oclif/dev-cli is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

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: >=8.10.0

Age: 7 years
Dependencies: 13 Direct
Versions: 161
Install Size: 84 kB
Dist-tags: 1
# of Files: 48
Maintainers: 3
TS Typings: Yes

@oclif/dev-cli 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.

Not sure how to use @oclif/dev-cli?

To help you get started, we've collected the most common ways that @oclif/dev-cli is being used within popular public projects.

balena-io / balena-cli / automation / build-bin.ts View on Github

if (packOS) {
		console.log(`Building oclif installer for CLI ${version}`);
		const packCmd = `pack:${packOS}`;
		const dirs = [path.join(ROOT, 'dist', packOS)];
		if (packOS === 'win') {
			dirs.push(path.join(ROOT, 'tmp', 'win*'));
		}
		for (const dir of dirs) {
			console.log(`rimraf(${dir})`);
			await Bluebird.fromCallback(cb => rimraf(dir, cb));
		}
		console.log('=======================================================');
		console.log(`oclif-dev "${packCmd}" "${packOpts.join('" "')}"`);
		console.log(`cwd="${process.cwd()}" ROOT="${ROOT}"`);
		console.log('=======================================================');
		await oclifRun([packCmd].concat(...packOpts));
		await renameInstallerFiles();
		// The Windows installer is explicitly signed here (oclif doesn't do it).
		// The macOS installer is automatically signed by oclif (which runs the
		// `pkgbuild` tool), using the certificate name given in package.json
		// (`oclif.macos.sign` section).
		if (process.platform === 'win32') {
			await signWindowsInstaller();
		}
		console.log(`oclif installer build completed`);
	}
}

View more ways to use @oclif/dev-cli

@oclif/dev-cli

helpers for oclif CLIs

Usage

$ npm install -g @oclif/dev-cli
$ oclif-dev COMMAND
running command...
$ oclif-dev (-v|--version|version)
@oclif/dev-cli/1.26.10 linux-x64 node-v14.18.2
$ oclif-dev --help [COMMAND]
USAGE
  $ oclif-dev COMMAND
...

Commands

`oclif-dev help [COMMAND]`

display help for oclif-dev

USAGE
  $ oclif-dev help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI

See code: @oclif/plugin-help

`oclif-dev manifest [PATH]`

generates plugin manifest json

USAGE
  $ oclif-dev manifest [PATH]

ARGUMENTS
  PATH  [default: .] path to plugin

See code: src/commands/manifest.ts

`oclif-dev pack`

packages oclif cli into tarballs

USAGE
  $ oclif-dev pack

OPTIONS
  -r, --root=root        (required) [default: .] path to oclif CLI root
  -t, --targets=targets  comma-separated targets to pack (e.g.: linux-arm,win32-x64)
  --[no-]xz              also build xz

DESCRIPTION
  This can be used to create oclif CLIs that use the system node or that come preloaded with a node binary.

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

`oclif-dev pack:deb`

pack CLI into debian package

USAGE
  $ oclif-dev pack:deb

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/pack/deb.ts

`oclif-dev pack:macos`

pack CLI into MacOS .pkg

USAGE
  $ oclif-dev pack:macos

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/pack/macos.ts

`oclif-dev pack:win`

create windows installer from oclif CLI

USAGE
  $ oclif-dev pack:win

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/pack/win.ts

`oclif-dev publish`

publish an oclif CLI to S3

USAGE
  $ oclif-dev publish

OPTIONS
  -r, --root=root        (required) [default: .] path to oclif CLI root
  -t, --targets=targets  comma-separated targets to pack (e.g.: linux-arm,win32-x64)

DESCRIPTION
  "aws-sdk" will need to be installed as a devDependency to publish.

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

`oclif-dev publish:deb`

publish deb package built with pack:deb

USAGE
  $ oclif-dev publish:deb

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/publish/deb.ts

`oclif-dev publish:macos`

publish macos installers built with pack:macos

USAGE
  $ oclif-dev publish:macos

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/publish/macos.ts

`oclif-dev publish:win`

publish windows installers built with pack:win

USAGE
  $ oclif-dev publish:win

OPTIONS
  -r, --root=root  (required) [default: .] path to oclif CLI root

See code: src/commands/publish/win.ts

`oclif-dev readme`

adds commands to README.md in current directory

USAGE
  $ oclif-dev readme

OPTIONS
  --dir=dir  (required) [default: docs] output directory for multi docs
  --multi    create a different markdown page for each topic

DESCRIPTION
  The readme must have any of the following tags inside of it for it to be replaced or else it will do nothing:
  # Usage
  
  # Commands
  

  Customize the code URL prefix by setting oclif.repositoryPrefix in package.json.

See code: src/commands/readme.ts

@oclif/dev-cli dependencies

@oclif/command @oclif/config @oclif/errors @oclif/plugin-help cli-ux debug find-yarn-workspace-root fs-extra github-slugger lodash normalize-package-data qqjs tslib

FAQs

What is @oclif/dev-cli?

helpers for oclif CLIs. Visit Snyk Advisor to see a full health score report for @oclif/dev-cli, including popularity, security, maintenance & community analysis.

Is @oclif/dev-cli popular?

The npm package @oclif/dev-cli receives a total of 109,519 weekly downloads. As such, @oclif/dev-cli popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @oclif/dev-cli well maintained?

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

Is @oclif/dev-cli safe to use?

While scanning the latest version of @oclif/dev-cli, 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 19 November-2024, at 23:17 (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 (109,519)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @oclif/dev-cli?

@oclif/dev-cli

Usage

Commands

oclif-dev help [COMMAND]

oclif-dev manifest [PATH]

oclif-dev pack

oclif-dev pack:deb

oclif-dev pack:macos

oclif-dev pack:win

oclif-dev publish

oclif-dev publish:deb

oclif-dev publish:macos

oclif-dev publish:win

oclif-dev readme