lost

v8.3.1

LostGrid is a powerful grid system built in PostCSS that works with any preprocessor and even vanilla CSS.

MIT
Latest version published 3 years ago
    npm install lost
  

Package Health Score

59 / 100

Security

Security review needed
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
8.3.1 | 02/2019
Popular
  • 0
    H
  • 0
    M
  • 0
    L
8.2.1 | 03/2018
  • 0
    H
  • 0
    M
  • 0
    L
7.1.1 | 11/2016
  • 0
    H
  • 0
    M
  • 0
    L
6.8.1 | 06/2016
  • 0
    H
  • 0
    M
  • 0
    L
6.7.2 | 02/2016
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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 lost
Get started free

Popularity

Popular

Weekly Downloads (24,330)

Download trend
Dependents
199
GitHub Stars
4.5K
Forks
178
Contributors
30

Direct Usage Popularity

TOP 10%

The npm package lost receives a total of 24,330 downloads a week. As such, we scored lost popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package lost, we found that it has been starred 4,503 times, and that 199 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

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

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


Embed Package Health Score Badge

package health: 59/100 package health 59/100

Maintenance

Inactive

Commit Frequency

Open Issues
23
Open PR
3
Last Release
3 years ago
Last Commit
14 days ago

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

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
2 Direct
Versions
46
Install Size
463 kB
Dist-tags
3
# of Files
122
Maintainers
2
TS Typings
No

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