git-repo-name

v1.0.1

Get the repository name from the git remote origin URL.

MIT
Latest version published almost 2 years ago
    npm install git-repo-name
  

Package Health Score

51 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Recognized
Weekly Downloads (47,062)
Dependents
52
GitHub Stars
14
Forks
4
Contributors
2

The npm package git-repo-name receives a total of 47,062 downloads a week. As such, we scored git-repo-name popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package git-repo-name, we found that it has been starred 14 times, and that 52 other projects on the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Security

No known security issues

Security and license risk for recent versions


Direct Vulnerabilities

0.5.0
0.5.1
0.6.0
1.0.0
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.5.0
0.5.1
0.6.0
1.0.0
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.5.0
0.5.1
0.6.0
1.0.0
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

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

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like git-repo-name is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test git-repo-name
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
0
Merged PR
1
Open PR
0
Last Commit
2 years ago

Further analysis of the maintenance status of git-repo-name 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 git-repo-name 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
2
Funding
No
License
MIT

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like git-repo-name is missing a Code of Conduct.

Package

Node.js Compatibility
>=8

Age
7 years
Dependencies
1 Direct / 4 Total
Versions
13
Install Size
6.27 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
Yes

We detected a total of 4 direct & transitive dependencies for git-repo-name. See the full dependency tree of git-repo-name

git-repo-name 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.