@charlesfries/emberfire

v3.0.0

The officially supported adapter for using Firebase with Ember

MIT
Latest version published 1 year ago
    npm install @charlesfries/emberfire
  

Package Health Score

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

Popularity

Limited

Weekly Downloads (17)

Download trend
Dependents
18
GitHub Stars
691
Forks
295
Contributors
80

Direct Usage Popularity


The npm package @charlesfries/emberfire receives a total of 17 downloads a week. As such, we scored @charlesfries/emberfire popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package @charlesfries/emberfire, we found that it has been starred 691 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
Popular

Version

Release Date

02/2020

Direct Vulnerabilities

Popular
3.0.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

Popular
3.0.0
  • 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 @charlesfries/emberfire 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 @charlesfries/emberfire
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Open Issues
25
Open PR
13
Last Release
1 year ago
Last Commit
8 months ago

Further analysis of the maintenance status of @charlesfries/emberfire 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 @charlesfries/emberfire 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.

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.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
80
Funding
No

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


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Package

Node.js Compatibility
^4.5 || 6.* || 8.* || >= 10.*

Age
1 year
Dependencies
6 Direct
Versions
2
Install Size
222 kB
Dist-tags
1
# of Files
87
Maintainers
1
TS Typings
Yes

@charlesfries/emberfire 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.