npmpackage.info

Gathering detailed insights and metrics for conventional-commit-types-cli

Other packages similar to conventional-commit-types-cli

conventional-commit-types

3.0.0

List of conventional commit types.

@stoplight/types

14.1.1

Common typings for the Stoplight ecosystem.

conventional-commits-parser

6.0.0

Parse raw conventional commits.

git-semver-tags

8.0.0

Get all git semver tags of your repository in reverse chronological order.

Gathering detailed insights and metrics for conventional-commit-types-cli

conventional-commit-types-cli

CLI to list conventional commit types.

1.0.4

ISC

JavaScript

2.39 kB

3,072 3

Installations

npm install conventional-commit-types-cli

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Developer

AndersDJohnson

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

10.12.0

NPM Version

6.9.0 Statistics

10 Stars

16 Commits

2 Forks

2 Watching

1 Branches

1 Contributors

Updated on 25 May 2024

Bundle Size

5.77 kB

Minified

2.39 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

3,072

Last day

2,200%

Compared to previous day

Last week

-6.7%

Compared to previous week

Last month

63.2%

111

Compared to previous month

Last year

44.7%

563

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

chalk conventional-commit-types right-pad-keys

Versions

conventional-commit-types-cli

CLI to list conventional commit types per https://github.com/commitizen/conventional-commit-types. So you can remember them when you're committing.

Use

npx conventional-commit-types-cli

Outputs e.g.:

feat    	A new feature
fix     	A bug fix
docs    	Documentation only changes
style   	Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor	A code change that neither fixes a bug nor adds a feature
perf    	A code change that improves performance
test    	Adding missing tests or correcting existing tests
build   	Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
ci      	Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
chore   	Other changes that don't modify src or test files
revert  	Reverts a previous commit

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

Score

3

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More