Fully working project examples showing how to use BrowserSync in various ways
52%
Total Score
67
100
75
67
The latest release was in January 2017, with no releases in the last 12 months. This long release gap materially increases abandonment and compatibility risk despite the package's 16-release history.
The package has a prepublish lifecycle script, which adds build-time behavior that consumers should understand, although it is not by itself evidence of poor maintenance.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old package release, this points to limited current maintenance capacity.
There were no new or closed issues or pull requests in the last month, while 18 issues and 13 pull requests remain open. This suggests unresolved maintenance backlog and low recent responsiveness.
The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked repository is specifically the package's maintained source, even though name differences can occur in related repositories.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.