@types/chrome

v0.0.125

TypeScript definitions for Chrome extension development

MIT
Latest version published 6 days ago
    npm install @types/chrome
  

Package Health Score

87 / 100
  • Popularity
    Influential project
  • Maintenance
    Healthy
  • Security
    No known security issues
  • Community
    Active

Popularity

Influential project
Weekly Downloads (116,834)
Dependents
311
GitHub Stars
30.41K
Forks
22.96K
Contributors
402

The npm package @types/chrome receives a total of 116,834 downloads a week. As such, we scored @types/chrome popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @types/chrome, we found that it has been starred 30,409 times, and that 311 other projects on 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

Security and license risk for recent versions


Direct Vulnerabilities

0.0.121
0.0.122
0.0.123
0.0.124
0.0.125
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.121
0.0.122
0.0.123
0.0.124
0.0.125
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.121
0.0.122
0.0.123
0.0.124
0.0.125
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

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

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

    # Install the Snyk CLI and test your project
npm i snyk && snyk test @types/chrome
Fix it in your project with Snyk!

Maintenance

Healthy
Commit Frequency
Open Issues
3.49K
Merged PR
35.06K
Open PR
307
Last Commit
13 hours ago

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

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

Community

Active
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
402
Funding
No
License
MIT

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

Package

Node.js Compatibility
not defined

Age
4 years
Dependencies
2 Direct / 3 Total
Versions
10
Install Size
510 kB
Dist-tags
23
# of Files
8
Maintainers
1
TS Typings
No

We detected a total of 3 direct & transitive dependencies for @types/chrome. See the full dependency tree of @types/chrome

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