@superset-ui/legacy-plugin-chart-chord

v0.16.3

Superset Legacy Chart - Chord Diagram

Apache-2.0
Latest version published 2 months ago
    npm install @superset-ui/legacy-plugin-chart-chord
  
We couldn't find any similar packages Browse all packages

Package Health Score

69 / 100
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Small

Weekly Downloads (1,958)

Dependents
52
GitHub Stars
147
Forks
120
Contributors
40

The npm package @superset-ui/legacy-plugin-chart-chord receives a total of 1,958 downloads a week. As such, we scored @superset-ui/legacy-plugin-chart-chord popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @superset-ui/legacy-plugin-chart-chord, we found that it has been starred 147 times, and that 52 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

Direct Vulnerabilities

0.12.21
0.13.30
0.14.23
0.15.19
0.16.3
  • 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.12.21
0.13.30
0.14.23
0.15.19
0.16.3
  • 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.12.21
0.13.30
0.14.23
0.15.19
0.16.3
  • 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
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
Apache-2.0

Security Policy
No

We found a way for you to contribute to the project! Looks like @superset-ui/legacy-plugin-chart-chord 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 && snyk test @superset-ui/legacy-plugin-chart-chord
Keep your project free of vulnerabilities with Snyk

Maintenance

Sustainable

Commit Frequency

Open Issues
58
Merged PR
575
Open PR
21
Last Commit
2 months ago

Further analysis of the maintenance status of @superset-ui/legacy-plugin-chart-chord based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that @superset-ui/legacy-plugin-chart-chord 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.

Community

Limited
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
40
Funding
No

With more than 10 contributors for the @superset-ui/legacy-plugin-chart-chord 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 @superset-ui/legacy-plugin-chart-chord is missing a Code of Conduct.

How about a good first contribution to this project? It seems that @superset-ui/legacy-plugin-chart-chord is missing a README file.


Embed Package Health Score Badge

package health: 69/100 package health 69/100

Package

Node.js Compatibility
not defined

Age
2 years
Dependencies
5 Direct / 102 Total
Versions
47
Install Size
323 kB
Dist-tags
1
# of Files
19
Maintainers
14
TS Typings
No

We detected a total of 102 direct & transitive dependencies for @superset-ui/legacy-plugin-chart-chord. See the full dependency tree of @superset-ui/legacy-plugin-chart-chord

@superset-ui/legacy-plugin-chart-chord 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.