1. Advisor
  2. JavaScript packages
  3. lost

lost

v9.0.2

LostGrid is a powerful grid system built in PostCSS that works with any preprocessor and even vanilla CSS. For more information about how to use this package see README

Latest version published 1 year ago
License: MIT
NPM
GitHub

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

65 / 100

Security

No known security issues
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
9.0.2 | 08/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.3.1 | 02/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
7.1.1 | 11/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.8.1 | 06/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.7.2 | 02/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 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.

Get started free

Popularity

Popular

Weekly Downloads (17,743)

Download trend
GitHub Stars
4.5K
Forks
160
Contributors
30

Direct Usage Popularity

TOP 5%

The npm package lost receives a total of 17,743 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,502 times.

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
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: 65/100 package health 65/100

Maintenance

Inactive

Commit Frequency

Open Issues
19
Open PR
2
Last Release
1 year ago
Last Commit
9 months 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.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
not defined
Age
11 years
Dependencies
1 Direct
Versions
51
Install Size
463 kB
Dist-tags
4
# of Files
128
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.