apify-shared

v0.7.6

Tools and constants shared across Apify projects. For more information about how to use this package see README

Latest version published 3 years ago
License: Apache-2.0

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

58 / 100

Security

Security review needed
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
0.7.6 | 04/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.6.3 | 03/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.5.9 | 02/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.6 | 10/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.72 | 02/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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 (5,152)

Download trend
GitHub Stars
10
Forks
9
Contributors
40

Direct Usage Popularity

Uncommon

The npm package apify-shared receives a total of 5,152 downloads a week. As such, we scored apify-shared popularity level to be Small.

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

With more than 10 contributors for the apify-shared 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 apify-shared is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive

Commit Frequency

Open Issues
5
Open PR
7
Last Release
3 years ago
Last Commit
13 days ago

Further analysis of the maintenance status of apify-shared 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 apify-shared 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.

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.

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
14 Direct
Versions
188
Install Size
233 kB
Dist-tags
2
# of Files
56
Maintainers
13
TS Typings
Yes

apify-shared 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.