The npm package loopback-datasource-juggler receives a total of 81,456 downloads a week. As such, we scored loopback-datasource-juggler popularity level to be Recognized.
Based on project statistics from the GitHub repository for the npm package loopback-datasource-juggler, we found that it has been starred 265 times, and that 429 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.
Snyk detected that the latest version of loopback-datasource-juggler 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 loopback-datasource-juggler is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test loopback-datasource-juggler
Further analysis of the maintenance status of loopback-datasource-juggler based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.
We found that loopback-datasource-juggler 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.
A good and healthy external contribution signal for loopback-datasource-juggler project, which invites more than one hundred open source maintainers to collaborate on the repository.
We found a way for you to contribute to the project! Looks like loopback-datasource-juggler is missing a Code of Conduct.
We detected a total of 89 direct & transitive dependencies for loopback-datasource-juggler. See the full dependency tree of loopback-datasource-juggler
loopback-datasource-juggler 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.