bem-naming

v1.0.1

Manage naming of BEM entities

MPL-2.0
Latest version published 6 years ago
    npm install bem-naming
  

Package Health Score

53 / 100

Security

No known security issues
Powered by Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
1.0.1 | 03/2016
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.5.1 | 01/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.4.0 | 11/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.3.0 | 08/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.2.1 | 08/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MPL-2.0
Alert

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.

Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test bem-naming
Get started free

Popularity

Small

Weekly Downloads (1,166)

Download trend
Dependents
0
GitHub Stars
83
Forks
24
Contributors
40

Direct Usage Popularity


The npm package bem-naming receives a total of 1,166 downloads a week. As such, we scored bem-naming popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package bem-naming, we found that it has been starred 83 times, and that 0 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.

Community

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

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
48
Open PR
7
Last Release
6 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of bem-naming 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 bem-naming 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.

Package

Node.js Compatibility
>= 4.0

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

bem-naming 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.