meta

v2.2.25

tool for turning many repos into a meta repo. why choose many repos or a monolithic repo, when you can have both with a meta repo?

MIT
Latest version published 1 year ago
    npm install meta
  
We couldn't find any similar packages Browse all packages

Package Health Score

54 / 100

Security

Security review needed
Powered by Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
2.2.25 | 04/2021
Popular
  • 0
    H
  • 0
    M
  • 0
    L
2.1.0 | 06/2019
  • 0
    H
  • 0
    M
  • 0
    L
1.2.19 | 05/2019
  • 0
    H
  • 0
    M
  • 0
    L
0.0.6 | 06/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test meta
Get started free

Popularity

Small

Weekly Downloads (1,500)

Download trend
Dependents
3
GitHub Stars
1.72K
Forks
74
Contributors
20

Direct Usage Popularity


The npm package meta receives a total of 1,500 downloads a week. As such, we scored meta popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package meta, we found that it has been starred 1,716 times, and that 3 other projects in 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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the meta 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 meta is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
9
Open PR
7
Last Release
1 year ago
Last Commit
1 year ago

Further analysis of the maintenance status of meta 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 meta 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.

Package

Node.js Compatibility
not defined

Age
10 years
Dependencies
9 Direct
Versions
112
Install Size
38.5 kB
Dist-tags
1
# of Files
25
Maintainers
2
TS Typings
No

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