@types/fscreen

v1.0.1

TypeScript definitions for fscreen

MIT
Latest version published 3 years ago
    npm install @types/fscreen
  
We couldn't find any similar packages Browse all packages

Package Health Score

68 / 100

Popularity

Popular

Weekly Downloads (17,664)

Download trend
Dependents
347
GitHub Stars
36.39K
Forks
26K
Contributors
410

Direct Usage Popularity

TOP 30%

The npm package @types/fscreen receives a total of 17,664 downloads a week. As such, we scored @types/fscreen popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @types/fscreen, we found that it has been starred 36,390 times, and that 347 other projects in the ecosystem are dependent on it.

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

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

08/2018

Direct Vulnerabilities

Popular
1.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
1.0.1
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like @types/fscreen is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test @types/fscreen
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
522
Open PR
253
Last Release
3 years ago
Last Commit
1 day ago

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

Community

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

A good and healthy external contribution signal for @types/fscreen 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 @types/fscreen is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 68/100 package health 68/100

Package

Node.js Compatibility
not defined

Age
4 years
Dependencies
0 Direct
Versions
3
Install Size
3.62 kB
Dist-tags
27
# of Files
4
Maintainers
1
TS Typings
No

@types/fscreen 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.