Package Health Score

62 / 100

security
No known security issues
popularity
Popular
maintenance
Inactive
community
Sustainable

Explore Similar Packages

Security

No known security issues

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

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
6.0.3	\|	12/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.0.0	\|	01/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.0.0	\|	01/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.3.8	\|	10/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.2.0	\|	10/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 (320,412)

GitHub Stars: 133
Forks: 25
Contributors: 20

Direct Usage Popularity

The npm package @semantic-release/exec receives a total of 320,412 downloads a week. As such, we scored @semantic-release/exec popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @semantic-release/exec, we found that it has been starred 133 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: 20
Funding: No

With more than 10 contributors for the @semantic-release/exec 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 @semantic-release/exec is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

Open Issues: 21
Open PR: 16
Last Release: 3 years ago
Last Commit: 6 months ago

Further analysis of the maintenance status of @semantic-release/exec 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 @semantic-release/exec 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.

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.17

Age: 7 years
Dependencies: 6 Direct
Versions: 51
Install Size: 25.5 kB
Dist-tags: 3
# of Files: 8
Maintainers: 4
TS Typings: No

@semantic-release/exec 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

@semantic-release/exec

semantic-release plugin to execute custom shell commands.

Step	Description
`verifyConditions`	Execute a shell command to verify if the release should happen.
`analyzeCommits`	Execute a shell command to determine the type of release.
`verifyRelease`	Execute a shell command to verifying a release that was determined before and is about to be published.
`generateNotes`	Execute a shell command to generate the release note.
`prepare`	Execute a shell command to prepare the release.
`publish`	Execute a shell command to publish the release.
`success`	Execute a shell command to notify of a new release.
`fail`	Execute a shell command to notify of a failed release.

Install

$ npm install @semantic-release/exec -D

Usage

The plugin can be configured in the semantic-release configuration file:

{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    ["@semantic-release/exec", {
      "verifyConditionsCmd": "./verify.sh",
      "publishCmd": "./publish.sh ${nextRelease.version} ${options.branch} ${commits.length} ${Date.now()}"
    }],
  ]
}

With this example:

the shell command ./verify.sh will be executed on the verify conditions step
the shell command ./publish.sh 1.0.0 master 3 870668040000 (for the release of version 1.0.0 from branch master with 3 commits on August 4th, 1997 at 2:14 AM) will be executed on the publish step

Note: it's required to define a plugin for the analyze commits step. If no analyzeCommitsCmd is defined the plugin @semantic-release/commit-analyzer must be defined in the plugins list.

Configuration

Options

Options	Description
`verifyConditionsCmd`	The shell command to execute during the verify condition step. See verifyConditionsCmd.
`analyzeCommitsCmd`	The shell command to execute during the analyze commits step. See analyzeCommitsCmd.
`verifyReleaseCmd`	The shell command to execute during the verify release step. See verifyReleaseCmd.
`generateNotesCmd`	The shell command to execute during the generate notes step. See generateNotesCmd.
`prepareCmd`	The shell command to execute during the prepare step. See prepareCmd.
`addChannelCmd`	The shell command to execute during the add channel step. See addChannelCmd.
`publishCmd`	The shell command to execute during the publish step. See publishCmd.
`successCmd`	The shell command to execute during the success step. See successCmd.
`failCmd`	The shell command to execute during the fail step. See failCmd.
`shell`	The shell to use to run the command. See execa#shell.
`execCwd`	The path to use as current working directory when executing the shell commands. This path is relative to the path from which semantic-release is running. For example if semantic-release runs from `/my-project` and `execCwd` is set to `buildScripts` then the shell command will be executed from `/my-project/buildScripts`

Each shell command is generated with Lodash template. All the objects passed to the semantic-release plugins are available as template options.

verifyConditionsCmd

Execute a shell command to verify if the release should happen.

Command property	Description
`exit code`	`0` if the verification is successful, or any other exit code otherwise.
`stdout`	Write only the reason for the verification to fail.
`stderr`	Can be used for logging.

analyzeCommitsCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	Only the release type (`major`, `minor` or `patch` etc..) can be written to `stdout`. If no release has to be done the command must not write to `stdout`.
`stderr`	Can be used for logging.

verifyReleaseCmd

Command property	Description
`exit code`	`0` if the verification is successful, or any other exit code otherwise.
`stdout`	Only the reason for the verification to fail can be written to `stdout`.
`stderr`	Can be used for logging.

generateNotesCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	Only the release note must be written to `stdout`.
`stderr`	Can be used for logging.

prepareCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	Can be used for logging.
`stderr`	Can be used for logging.

addChannelCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	The `release` information can be written to `stdout` as parseable JSON (for example `{"name": "Release name", "url": "https://url/release/1.0.0"}`). If the command write non parseable JSON to `stdout` no `release` information will be returned.
`stderr`	Can be used for logging.

publishCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	The `release` information can be written to `stdout` as parseable JSON (for example `{"name": "Release name", "url": "https://url/release/1.0.0"}`). If the command write non parseable JSON to `stdout` no `release` information will be returned.
`stderr`	Can be used for logging.

successCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	Can be used for logging.
`stderr`	Can be used for logging.

failCmd

Command property	Description
`exit code`	Any non `0` code is considered as an unexpected error and will stop the `semantic-release` execution with an error.
`stdout`	Can be used for logging.
`stderr`	Can be used for logging.

@semantic-release/exec dependencies

@semantic-release/error aggregate-error debug execa lodash parse-json

@semantic-release/exec development dependencies

ava nyc semantic-release sinon stream-buffers xo

FAQs

What is @semantic-release/exec?

semantic-release plugin to run custom shell commands. Visit Snyk Advisor to see a full health score report for @semantic-release/exec, including popularity, security, maintenance & community analysis.

Is @semantic-release/exec popular?

The npm package @semantic-release/exec receives a total of 320,412 weekly downloads. As such, @semantic-release/exec popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @semantic-release/exec well maintained?

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

Is @semantic-release/exec safe to use?

The npm package @semantic-release/exec was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 3 November-2024, at 01:33 (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