pp365-portfoliowebparts

v1.8.4

_Published to **npm** as `pp365-portfoliowebparts`_ For more information about how to use this package see README

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

59 / 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
1.8.4 | 08/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.7.3 | 11/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.7.2 | 10/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.6.7 | 10/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.5.4 | 04/2022
  • 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

Limited

Weekly Downloads (10)

Download trend
GitHub Stars
29
Forks
16
Contributors
20

Direct Usage Popularity


The npm package pp365-portfoliowebparts receives a total of 10 downloads a week. As such, we scored pp365-portfoliowebparts popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package pp365-portfoliowebparts, we found that it has been starred 29 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
20
Funding
No

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


Embed Package Health Score Badge

package health: 59/100 package health 59/100

Maintenance

Sustainable

Commit Frequency

Open Issues
51
Open PR
0
Last Release
1 year ago
Last Commit
14 days ago

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

An important project maintenance signal to consider for pp365-portfoliowebparts 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
4 years
Dependencies
34 Direct
Versions
132
Install Size
37.5 MB
Dist-tags
2
# of Files
878
Maintainers
3
TS Typings
No

pp365-portfoliowebparts 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.