@joplin/renderer

v3.0.1

The Joplin note renderer, used the mobile and desktop application For more information about how to use this package see README

Latest version published 4 months ago
License: AGPL-3.0-or-later

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

78 / 100

Security

Security review needed
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.0.1 | 07/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.14.1 | 03/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.13.3 | 11/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.8.2 | 05/2021
  • 0
    H
  • 0
    M
  • 0
    L
1.7.5 | 01/2021
  • 0
    H
  • 0
    M
  • 0
    L
License
AGPL-3.0-or-later
Security Policy
Yes

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

Small

Weekly Downloads (858)

Download trend
GitHub Stars
45.8K
Forks
4.97K
Contributors
440

Direct Usage Popularity

TOP 30%

The npm package @joplin/renderer receives a total of 858 downloads a week. As such, we scored @joplin/renderer popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @joplin/renderer, we found that it has been starred 45,797 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
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
440
Funding
Yes

A good and healthy external contribution signal for @joplin/renderer project, which invites more than one hundred open source maintainers to collaborate on the repository.

We found a way for you to contribute to the project! Looks like @joplin/renderer is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 78/100 package health 78/100

Maintenance

Healthy

Commit Frequency

Open Issues
429
Open PR
15
Last Release
4 months ago
Last Commit
9 days ago

Further analysis of the maintenance status of @joplin/renderer based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @joplin/renderer demonstrates a positive version release cadence with at least one new version released in the past 12 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.

Package

Node.js Compatibility
not defined

Age
4 years
Dependencies
24 Direct
Versions
40
Install Size
4.19 MB
Dist-tags
1
# of Files
153
Maintainers
3
TS Typings
Yes

@joplin/renderer 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.