Package Health Score

70 / 100

security
Security review needed
popularity
Limited
maintenance
Healthy
community
Sustainable

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version			Vulnerabilities	License Risk
2.5.2	\|	12/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.4.0	\|	09/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.30.0	\|	01/2024	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.21.0	\|	10/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.20.0	\|	10/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Unknown

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.

Security Policy

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

Limited

Weekly Downloads (120)

GitHub Stars: 2
Forks: 0
Contributors: 20

Direct Usage Popularity

The npm package grep-components receives a total of 120 downloads a week. As such, we scored grep-components popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package grep-components, we found that it has been starred 2 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: No
Code of Conduct: No
Contributors: 20
Funding: No

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

How about a good first contribution to this project? It seems that grep-components is missing a LICENSE file.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 0
Open PR: 1
Last Release: 20 days ago
Last Commit: 20 days ago

Further analysis of the maintenance status of grep-components based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that grep-components demonstrates a positive version release cadence with at least one new version released in the past 3 months.

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.

Keep your project healthy

Check your package.json

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

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=8

Age: 6 years
Dependencies: 8 Direct
Versions: 533
Install Size: 1.78 MB
Dist-tags: 91
# of Files: 151
Maintainers: 3
TS Typings: No

grep-components 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.

Readme

Komponentbibliotek

Komponentbibliotek for Grep. Brukes i Læreplanutvikleren og Grepadmin.

Installation

npm i grep-components

Features

Bundles cjs and es module formats
create-react-app for example usage and local dev
Rollup for bundling
Babel for transpiling
Jest & React Testing Library for testing
Typescript
Sourcemap creation
Storybook for easy development of components
commitlint to enforce the conventional commit format
semantic-release for version management and package publishing
Github Actions for running build, test and release jobs
Dependabot for dependency management

Publishing

Pushing to master or any feature-branch (feature/some-feature) will automatically run the release-workflow. This will build the package, analyze the commits to determine next version number and publish the new version to NPM and Github. Current and previous runs can be seen here.

Semantic-release will determine the next version number by looking at the commit message prefix:

Prefix	Release type	Example commit message
'BREAKING CHANGE: ' in commit message footer	Major release	revert: Reverting some changes BREAKING CHANGE: this revert will break something
feat	Minor release	feat: Some minor changes
fix, perf, revert, refactor, build/chore(deps*)	Patch release	fix: Some fixes

If a commit contains none of these, then no release will be created / published.

The release-workflow can also be manually triggered from here, but will still only release if there is a commit with a valid prefix.

Important

Feature-branches have to start with feature/ to be included in the release-workflow. Example: feature/some-feature
Published versions from a valid feature-branch will get the branch-name, excluding the feature/ part, as a dist-tag in NPM. Example: feature/some-feature on version 0.18.0 will become 0.18.0-some-feature.1 and can be installed by running npm i grep-components@some-feature

grep-components dependencies

@emotion/react @emotion/styled @lexical/react @mui/icons-material @mui/material @mui/x-date-pickers dayjs lexical

grep-components development dependencies

@babel/core @babel/eslint-parser @babel/plugin-transform-private-property-in-object @chromatic-com/storybook @commitlint/cli @commitlint/config-conventional @hello-pangea/dnd @lexical/html @lexical/utils @rollup/plugin-commonjs @rollup/plugin-json @rollup/plugin-node-resolve @rollup/plugin-typescript @rollup/plugin-url @storybook/addon-actions @storybook/addon-essentials @storybook/addon-links @storybook/addon-storysource @storybook/cli @storybook/preset-create-react-app @storybook/preview-api @storybook/react-webpack5 @storybook/storybook-deployer @testing-library/dom @testing-library/jest-dom @testing-library/react @testing-library/user-event @types/history @types/jest @types/lodash.debounce @types/lodash.throttle @types/react @types/react-dom @types/react-redux @types/react-router-dom @typescript-eslint/eslint-plugin @typescript-eslint/parser babel-jest babel-loader babel-plugin-external-helpers babel-runtime chalk clsx commitlint conventional-changelog-cli cross-env eslint eslint-plugin-jest-dom eslint-plugin-react eslint-plugin-storybook eslint-plugin-testing-library husky jest jest-environment-jsdom lint-staged lodash.debounce lodash.throttle prettier react react-dom react-redux react-router-dom react-scripts rollup rollup-plugin-peer-deps-external rollup-plugin-postcss seamless-immutable semantic-release storybook ts-jest ts-keycode-enum tslib tss-react typescript

FAQs

What is grep-components?

Grep komponentbibliotek. Visit Snyk Advisor to see a full health score report for grep-components, including popularity, security, maintenance & community analysis.

Is grep-components popular?

The npm package grep-components receives a total of 120 weekly downloads. As such, grep-components popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is grep-components well maintained?

We found that grep-components demonstrated a healthy version release cadence and project activity. It has a community of 20 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is grep-components safe to use?

While scanning the latest version of grep-components, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 23 December-2024, at 20:13 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

grep-components

Grep komponentbibliotek For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Security

Security and license risk for significant versions

Unable to detect license

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (120)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Readme

Komponentbibliotek

Installation

Features

Publishing

Important

grep-components dependencies

grep-components development dependencies

FAQs

What is grep-components?

Is grep-components popular?

Is grep-components well maintained?

Is grep-components safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (120)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

Komponentbibliotek

Installation

Features

Publishing

Important

grep-components dependencies

grep-components development dependencies

FAQs

What is grep-components?

Is grep-components popular?

Is grep-components well maintained?

Is grep-components safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues