Gathering detailed insights and metrics for tagger-bin
Gathering detailed insights and metrics for tagger-bin
Gathering detailed insights and metrics for tagger-bin
Gathering detailed insights and metrics for tagger-bin
npm install tagger-bin
Typescript
Module System
Node Version
NPM Version
Rust (89.87%)
JavaScript (5.08%)
Shell (5.05%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
2 Stars
13 Commits
4 Branches
1 Contributors
Updated on Feb 21, 2020
Latest Version
1.0.5
Package Id
tagger-bin@1.0.5
Unpacked Size
13.03 MB
Size
4.41 MB
File Count
7
NPM Version
6.4.1
Node Version
8.12.0
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
No dependencies detected.
Simple utility to do something (e.g. install) packages from git repository by selecting git tag which is presented by semver rules.
Tagger works with git repositories only through ssh connection.
If you have a package that is not in npm or local repos but it has versionong, tagger
may be helpful for you.
tagger
works with:
// TODO
Usage: tagger (--help | --version)
tagger [--cfg PATH] (--show-latest | --list-all) PACKAGES...
tagger [--exec --cfg PATH] PACKAGES...
Options:
-h, --help Show this message.
-v, --version Show the version of tagger.
-c PATH, --cfg PATH Path to config file. If not specified config will be searching in ./.tagger.cfg.json and ~/.tagger.cfg.json"
-l, --show-latest Prints latest valid tag.
-a, --list-all Prints all valid by semver tags.
-e, --exec *optional. Do something with specified or latest package version.
Examples:
tagger ui
tagger --show-latest hlp
tagger --exec -c ../path_to_tagger_config.json hlp@2.1.3
Config file name by default is .tagger.cfg.json
. And if it is not specified, it is searched in directory where you run tagger
or in your home directory (e.g. ~/.tagger.cfg.json
).
Config includes fields:
repos
Type: Array<{name: string, url: string}>
List of package repositories you want to use. Each item in this list cantains name
( to identify it )
and url
know how to connect.
Example:
1{ 2 "repos": [ 3 { 4 "name": "tagger", 5 "url": "ssh://git@github.com:emgyrz/tagger.git" 6 } 7 ], 8 // ... 9}
command
Type: String
Says what to do with package. In command
you have several variables that will be replaced on executing
{NAME}
- name of package presents in repo{URL}
- same{VERSION}
- version of package you were specify or latest versionExample:
1{ 2 // ... 3 "command": "yarn add {URL}#{VERSION}" 4 // "command": "echo 'my latest version of package {NAME} is {VERSION}'", 5 // "command": "rm -rf / :)" 6}
This package is MIT licensed.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
Found 0/13 approved changesets -- 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
13 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
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