Dependents

27

GitHub Stars

573

Forks

155

Contributors

20

The npm package angular-split receives a total of 39,970 downloads a week. As such, we scored angular-split popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package angular-split, we found that it has been starred 573 times, and that 27 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.

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

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

    # Install the Snyk CLI and test your project
npm i snyk && snyk test angular-split 
          copy
        
  

Open Issues

27

Merged PR

42

Open PR

4

Last Commit

2 months ago

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

We found that angular-split demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

Readme.md

Yes

Contributing.md

No

Code of Conduct

No

Contributors

20

Funding

Yes

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

Embed Package Health Score Badge

Copy Markdown

Node.js Compatibility

not defined

Age

4 years

Dependencies

1 Direct

Versions

78

Install Size

630 kB

Dist-tags

2

# of Files

24

Maintainers

1

TS Typings

No

angular-split 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.