1. Advisor
  2. JavaScript packages
  3. myst-config

myst-config

v1.7.5

Project and site config types and validation for the mystmd ecosystem For more information about how to use this package see README

Latest version published 1 month ago
License: MIT
NPM
GitHub

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

82 / 100

Security

No known security issues
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
1.7.5 | 11/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.6.1 | 09/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.17 | 11/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.16 | 06/2023
  • 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.

Get started free

Popularity

Limited

Weekly Downloads (125)

Download trend
GitHub Stars
222
Forks
65
Contributors
50

Direct Usage Popularity

The npm package myst-config receives a total of 125 downloads a week. As such, we scored myst-config popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package myst-config, we found that it has been starred 222 times.

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

Community

Active
Readme.md
No
Contributing.md
Yes
Code of Conduct
No
Contributors
50
Funding
No

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

How about a good first contribution to this project? It seems that myst-config is missing a README file.

Embed Package Health Score Badge

package health: 82/100 package health 82/100

Maintenance

Healthy

Commit Frequency

Open Issues
386
Open PR
18
Last Release
1 month ago
Last Commit
15 days ago

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

We found that myst-config demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
2 years
Dependencies
3 Direct
Versions
79
Install Size
23.6 kB
Dist-tags
1
# of Files
32
Maintainers
2
TS Typings
No

myst-config 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.