occlusion

v0.0.1

it's a matter of perspective For more information about how to use this package see README

Latest version published 1 year ago
License: MIT

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

56 / 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
0.0.1 | 08/2023
Popular
  • 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 (0)

Download trend
GitHub Stars
3
Forks
2
Contributors
4

Direct Usage Popularity


The npm package occlusion receives a total of 0 downloads a week. As such, we scored occlusion popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package occlusion, we found that it has been starred 3 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
No
Contributing.md
No
Code of Conduct
No
Contributors
4
Funding
No

This project has seen only 10 or less contributors.

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

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


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive

Commit Frequency

Open Issues
22
Open PR
2
Last Release
1 year ago
Last Commit
9 days ago

Further analysis of the maintenance status of occlusion 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 occlusion 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
2 years
Dependencies
3 Direct
Versions
3
Install Size
14.6 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

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