content-entry

v11.0.1

content entries for content containers (aka files) For more information about how to use this package see README

Latest version published 2 months ago
License: BSD-2-Clause

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

69 / 100

Explore Similar Packages

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
11.0.1 | 06/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.0.1 | 03/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.0.3 | 03/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.1.3 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.0.1 | 03/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-2-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.

Get started free

Popularity

Small

Weekly Downloads (5,333)

Download trend
GitHub Stars
0
Forks
0
Contributors
6

Direct Usage Popularity

TOP 30%

The npm package content-entry receives a total of 5,333 downloads a week. As such, we scored content-entry popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package content-entry, we found that it has been starred ? times.

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

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
6
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 69/100 package health 69/100

Maintenance

Healthy

Commit Frequency

Open Issues
0
Open PR
0
Last Release
2 months ago
Last Commit
13 days ago

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

We found that content-entry 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.

Package

Node.js Compatibility
>=20.12.2

Age
6 years
Dependencies
1 Direct
Versions
127
Install Size
38.2 kB
Dist-tags
2
# of Files
27
Maintainers
1
TS Typings
No

content-entry 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.