Gathering detailed insights and metrics for @semabit/release-it-bumper
Gathering detailed insights and metrics for @semabit/release-it-bumper
Gathering detailed insights and metrics for @semabit/release-it-bumper
Gathering detailed insights and metrics for @semabit/release-it-bumper
npm install @semabit/release-it-bumper
Typescript
Module System
Min. Node Version
Node Version
NPM Version
61.7
Supply Chain
90.3
Quality
73.6
Maintenance
50
Vulnerability
97.1
License
JavaScript (96.4%)
Handlebars (3.6%)
Total Downloads
10,983
Last Day
4
Last Week
41
Last Month
288
Last Year
2,630
38 Commits
1 Forks
2 Watching
1 Branches
2 Contributors
Latest Version
2.1.0
Package Id
@semabit/release-it-bumper@2.1.0
Unpacked Size
21.57 kB
Size
6.21 kB
File Count
9
NPM Version
6.14.10
Node Version
12.20.1
Publised On
06 Nov 2023
Cumulative downloads
Total Downloads
Last day
-73.3%
4
Compared to previous day
Last week
-43.1%
41
Compared to previous week
Last month
50%
288
Compared to previous month
Last year
-11.1%
2,630
Compared to previous year
4
This plugin reads and/or writes version/manifest files.
# npm
npm install --save-dev @semabit/release-it-bumper
# yarn
yarn add --dev @semabit/release-it-bumper
In release-it config:
1"plugins": { 2 "@semabit/release-it-bumper": { 3 "out": "manifest.json" 4 } 5}
for .yaml
file:
1"plugins": { 2 "@semabit/release-it-bumper": { 3 "out": { "file": "version.yaml", "type": "application/x-yaml" } 4 } 5}
In case the in
option is used, the version from this file will take precedence over the version
from package.json
or the latest Git tag (which release-it uses by default).
The default type
is application/json
, but text/plain
and application/x-yaml
are also supported.
In that case the whole file is used to read and/or write the version.
1"plugins": { 2 "@semabit/release-it-bumper": { 3 "in": { "file": "VERSION", "type": "text/plain" }, 4 "out": { "file": "VERSION", "type": "text/plain" } 5 } 6}
1"plugins": { 2 "@semabit/release-it-bumper": { 3 "in": { "file": "version.yaml", "type": "application/x-yaml" }, 4 "out": { "file": "version.yaml", "type": "application/x-yaml" } 5 } 6}
The out
option can also be an array of files:
1"plugins": { 2 "@semabit/release-it-bumper": { 3 "out": ["manifest.json", "bower.json", { "file": "version.yaml", "type": "application/x-yaml" }] 4 } 5}
The path
option (default: "version"
) can be used to change a different property. the following example will set the
deeper.current
property to the new version in manifest.json
. Also possible to define the path for yaml
files:
1"plugins": { 2 "@semabit/release-it-bumper": { 3 "out": [ 4 { "file": "manifest.json", "path": "deeper.current" }, 5 { "file": "version.yaml", "type": "application/x-yaml", "path": "parameters['app.version']" } 6 ] 7 } 8}
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
46 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-12-16
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