1. Advisor
  2. JavaScript packages
  3. @does/exist

@does/exist

v1.1.0

🗄 Check if a file exists For more information about how to use this package see README

Latest version published 5 years 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

51 / 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
1.1.0 | 12/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 12/2018
  • 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 (719)

Download trend
GitHub Stars
34
Forks
11
Contributors
30

Direct Usage Popularity

Uncommon

The npm package @does/exist receives a total of 719 downloads a week. As such, we scored @does/exist popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @does/exist, we found that it has been starred 34 times.

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
Yes
Contributors
30
Funding
No

With more than 10 contributors for the @does/exist repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
16
Last Release
5 years ago
Last Commit
2 months ago

Further analysis of the maintenance status of @does/exist 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 @does/exist 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.

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

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
6 years
Dependencies
0 Direct
Versions
3
Install Size
1.42 kB
Dist-tags
1
# of Files
3
Maintainers
1
TS Typings
No

@does/exist 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.