@types/classnames

v2.3.1

Stub TypeScript definitions entry for classnames, which provides its own types definitions For more information about how to use this package see README

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

63 / 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
2.3.1 | 04/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.2.11 | 10/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.32 | 11/2016
  • 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

Key ecosystem project

Weekly Downloads (1,369,344)

Download trend
Dependents
365
GitHub Stars
33.29K
Forks
24.49K
Contributors
410

Direct Usage Popularity

TOP 5%

The npm package @types/classnames receives a total of 1,369,344 downloads a week. As such, we scored @types/classnames popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package @types/classnames, we found that it has been starred 33,294 times, and that 365 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.

Community

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

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


Embed Package Health Score Badge

package health: 63/100 package health 63/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
3.66K
Open PR
237
Last Release
2 years ago
Last Commit
2 years ago

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

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
1 Direct
Versions
29
Install Size
1.66 kB
Dist-tags
25
# of Files
3
Maintainers
1
TS Typings
Yes

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