angularfire

v2.3.0

The officially supported AngularJS binding for Firebase

MIT
Latest version published 4 years ago
    npm install angularfire
  

Package Health Score

50 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Recognized
Download trend

Weekly Downloads (1,578)

Dependents
18
GitHub Stars
2.77K
Forks
677
Contributors
70

The npm package angularfire receives a total of 1,578 downloads a week. As such, we scored angularfire popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package angularfire, we found that it has been starred 2,771 times, and that 18 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.

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.9.2
1.2.0
2.2.0
2.3.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.9.2
1.2.0
2.2.0
2.3.0
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.9.2
1.2.0
2.2.0
2.3.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like angularfire 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 -g && snyk test angularfire
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
4 years ago
Last Commit
4 months ago

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

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
70
Funding
No

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


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Package

Node.js Compatibility
not defined

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

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