accessibility

v6.0.7

add accessibility to your website For more information about how to use this package see README

Latest version published 1 month 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

78 / 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
6.0.7 | 10/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.1.5 | 06/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.5.12 | 03/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.17 | 07/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.0 | 06/2019
  • 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

Small

Weekly Downloads (1,441)

Download trend
GitHub Stars
294
Forks
41
Contributors
20

Direct Usage Popularity

TOP 30%

The npm package accessibility receives a total of 1,441 downloads a week. As such, we scored accessibility popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package accessibility, we found that it has been starred 294 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
No
Code of Conduct
No
Contributors
20
Funding
No

With more than 10 contributors for the accessibility repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like accessibility is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 78/100 package health 78/100

Maintenance

Healthy

Commit Frequency

Open Issues
4
Open PR
3
Last Release
1 month ago
Last Commit
1 month ago

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

We found that accessibility demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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
8 years
Dependencies
1 Direct
Versions
81
Install Size
426 kB
Dist-tags
1
# of Files
45
Maintainers
1
TS Typings
Yes

accessibility 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.