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

@types/navermaps

v3.7.8

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

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

78 / 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
3.7.8 | 09/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.6.7 | 09/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.18 | 11/2022
  • 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

Recognized

Weekly Downloads (7,943)

Download trend
GitHub Stars
48.22K
Forks
30.04K
Contributors
400

Direct Usage Popularity

Uncommon

The npm package @types/navermaps receives a total of 7,943 downloads a week. As such, we scored @types/navermaps popularity level to be Recognized.

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

A good and healthy external contribution signal for @types/navermaps 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/navermaps 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
550
Open PR
163
Last Release
2 months ago
Last Commit
2 months ago

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

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

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
7 years
Dependencies
1 Direct
Versions
37
Install Size
78.9 kB
Dist-tags
40
# of Files
5
Maintainers
1
TS Typings
Yes

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