stanford-postagger

v1.1.5

Stanford Log-Linear Part-Of-Speech (POS) Tagger

MIT
Latest version published 1 year ago
    npm install stanford-postagger
  

Package Health Score

40 / 100

Security

Security review needed
Powered by Snyk
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.1.5 | 01/2021
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3 | 09/2018
  • 0
    H
  • 0
    M
  • 0
    L
0.9.5 | 06/2018
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test stanford-postagger
Get started free

Popularity

Limited

Weekly Downloads (30)

Download trend
Dependents
0
GitHub Stars
8
Forks
3
Contributors
1

Direct Usage Popularity

Uncommon

The npm package stanford-postagger receives a total of 30 downloads a week. As such, we scored stanford-postagger popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package stanford-postagger, we found that it has been starred 8 times, and that 0 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.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
1
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 40/100 package health 40/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1
Open PR
0
Last Release
1 year ago
Last Commit
1 year ago

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

Package

Node.js Compatibility
>=8.0.0

Age
4 years
Dependencies
5 Direct
Versions
17
Install Size
22.5 kB
Dist-tags
1
# of Files
7
Maintainers
1
TS Typings
No

stanford-postagger 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.