catalog

v3.6.2

Create living style guides using Markdown or React

BSD-3-Clause
Latest version published 12 months ago
    npm install catalog
  

Package Health Score

58 / 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
3.6.2 | 05/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.5.5 | 07/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.5.3 | 02/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0 | 11/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.12 | 11/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
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 catalog
Get started free

Popularity

Small

Weekly Downloads (1,203)

Download trend
Dependents
192
GitHub Stars
1.54K
Forks
156
Contributors
30

Direct Usage Popularity

TOP 30%

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

Based on project statistics from the GitHub repository for the npm package catalog, we found that it has been starred 1,537 times, and that 192 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
Yes
Code of Conduct
No
Contributors
30
Funding
No

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


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
81
Open PR
34
Last Release
12 months ago
Last Commit
2 years ago

Further analysis of the maintenance status of catalog based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that catalog demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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

Package

Node.js Compatibility
not defined

Age
9 years
Dependencies
46 Direct
Versions
146
Install Size
3.6 MB
Dist-tags
3
# of Files
41
Maintainers
1
TS Typings
Yes

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