pier

v0.0.0

replicate a seaport service registry for fast local in-memory access or redundancy

MIT
Latest version published over 8 years ago
    npm install pier
  

Package Health Score

35 / 100
  • Popularity
    Limited
  • Maintenance
    Inactive
  • Security
    Security review needed
  • Community
    Limited

Popularity

Limited
Weekly Downloads (0)
Dependents
0
GitHub Stars
13
Forks
1
Contributors
1

The npm package pier receives a total of 0 downloads a week. As such, we scored pier popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package pier, we found that it has been starred 13 times, and that 0 other projects on 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

Security review needed

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.0
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.0

License Risks

0.0.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

Snyk detected that the latest version of pier has a security vulnerability.

We highly advise you to review these security issues.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like pier is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test pier
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
0
Merged PR
0
Open PR
0
Last Commit
8 years ago

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

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
1
Funding
No
License
MIT

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 35/100 package health 35/100

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
1 Direct / 17 Total
Versions
1
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

We detected a total of 17 direct & transitive dependencies for pier. See the full dependency tree of pier

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