1. Advisor
  2. JavaScript packages
  3. @types/openfin

@types/openfin

v51.0.6

TypeScript definitions for openfin For more information about how to use this package see README

Latest version published 12 months 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

74 / 100

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
50.0.9 | 11/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
51.0.6 | 11/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
43.0.5 | 07/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
45.0.4 | 07/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
49.0.3 | 07/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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 (708)

Download trend
GitHub Stars
48.53K
Forks
30.15K
Contributors
400

Direct Usage Popularity

TOP 30%

The npm package @types/openfin receives a total of 708 downloads a week. As such, we scored @types/openfin popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @types/openfin, we found that it has been starred 48,530 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
No
Code of Conduct
No
Contributors
400
Funding
No

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

Embed Package Health Score Badge

package health: 74/100 package health 74/100

Maintenance

Sustainable

Commit Frequency

Open Issues
552
Open PR
168
Last Release
12 months ago
Last Commit
14 days ago

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

We found that @types/openfin 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.

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
8 years
Dependencies
4 Direct
Versions
87
Install Size
384 kB
Dist-tags
40
# of Files
131
Maintainers
1
TS Typings
Yes

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