Gathering detailed insights and metrics for @erikatakahara/mommit
Installations
npm install @erikatakahara/mommitDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
12.22.6
NPM Version
7.23.0
Score
66.9
Supply Chain
76.6
Quality
73.5
Maintenance
100
Vulnerability
98.6
License
Releases
6
Contributors
4
Unable to fetch Contributors
Languages
1
JavaScript
JavaScript (100%)
Developer
erikatakahara
Download Statistics
Total Downloads
1,466
Last Day
1
Last Week
11
Last Month
41
Last Year
173
GitHub Statistics
12 Stars
68 Commits
3 Forks
1 Watching
7 Branches
4 Contributors
Bundle Size
2.02 kB
Minified
955.00 B
Minified + Gzipped
Maintainers
1
Package Meta Information
Latest Version
1.5.0
Package Id
@erikatakahara/mommit@1.5.0
Unpacked Size
770.27 kB
Size
237.42 kB
File Count
10
NPM Version
7.23.0
Node Version
12.22.6
Total Downloads
Cumulative downloads
Total Downloads
1,466
Last day
0%
1
Compared to previous day
Last week
37.5%
11
Compared to previous week
Last month
241.7%
41
Compared to previous month
Last year
-39.5%
173
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
3
Dev Dependencies
2
Versions
mommit
A simple way and visual way to add co-authors on your commit!
Why mommit?
Because it's a pain to always write the co-authors following the correct format, so I made this simple git commit wrapper to be able to add co-authors with ease.
Install globally
npm install -g @erikatakahara/mommit
Usage
- If it's the first time you're commiting with the co-author, add them using
mommit add. - Them call
mommitcommand. Tip:-mand-afrom git works here ;) - Select the co-author and you're done!
mommit add
You have three ways to add an author to your mommit:
mommit add- manually add using the promptmommit add -l- select from a list of authors from git logmommit add -s- search for a single author from git log
mommit remove
If you want to remove an author from your list, just call mommit remove and select the ones you want to remove.
mommit list
If you want to see which users are already added, just call mommit list to see which users are stored inside mommit.
add jira code
If you want to add the JIRA code to your commit in the format [<ticket-number>] <commit-message>, create a branch starting with the ticket number and use the -j flag.
Example: using the command mommit -jam "Testing" on the branch MS-101-branch-description will git add the files and create a commit on the format [MS-101] Testing.
semantic release format
In case you use sematic release format, you can add -s flag.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/erikatakahara/mommit/lint.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/erikatakahara/mommit/publish.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/erikatakahara/mommit/publish.yml/master?enable=pin
- Info: 0 out of 3 GitHub-owned GitHubAction dependencies pinned
- Info: 2 out of 2 npmCommand dependencies pinned
Reason
Found 0/11 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/lint.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
license file not detected
Details
- Warn: project does not have a license file
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 29 are checked with a SAST tool
Reason
23 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-93q8-gq69-wqmw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-rc47-6667-2j5j
- Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-896r-f27r-55mw
- Warn: Project is vulnerable to: GHSA-5v2h-r2cx-5xgj
- Warn: Project is vulnerable to: GHSA-rrrm-qjm4-v8hf
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-r683-j2x4-v87g
- Warn: Project is vulnerable to: GHSA-hj9c-8jmm-8c52
- Warn: Project is vulnerable to: GHSA-hrpp-h998-j3pp
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-x2pg-mjhr-2m5x
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-4x5v-gmq8-25ch
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
Score
2.7
/10
Last Scanned on 2025-01-27
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