Gathering detailed insights and metrics for @limetech/lime-elements
Gathering detailed insights and metrics for @limetech/lime-elements
Provides reusable web components for Lime CRM
Installations
npm install @limetech/lime-elementsDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Node Version
20.19.1
NPM Version
10.8.2
Releases
1,229
Languages
6
TypeScript
SCSS
CSS
JavaScript
HTML
Handlebars
TypeScript (81.35%)
SCSS (16.5%)
CSS (1.37%)
JavaScript (0.61%)
HTML (0.13%)
Handlebars (0.04%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
NOASSERTION License
41 Stars
6,160 Commits
16 Forks
14 Watchers
100 Branches
38 Contributors
Updated on Jul 11, 2025
Maintainers
5
Package Meta Information
Latest Version
38.19.2
Package Id
@limetech/lime-elements@38.19.2
Unpacked Size
62.77 MB
Size
12.07 MB
File Count
1,521
NPM Version
10.8.2
Node Version
20.19.1
Published on
Jul 10, 2025
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
57
@commitlint/config-conventional@limetech/eslint-config@microsoft/api-extractor@popperjs/core@rjsf/core@rollup/plugin-node-resolve@stencil/core@stencil/sass@types/codemirror@types/html-escaper@types/jest@types/lodash-es@types/react@types/react-dom@types/tabulator-tablescodemirrorcross-envdayjseslintflatpickrglobalshtml-escaperjestjest-clijsonlint-modjsx-domkompendiumlodash-esmaterial-components-webmomentnumber-abbreviateparse-css-colorprettierprosemirror-example-setupprosemirror-markdownprosemirror-modelprosemirror-schema-basicprosemirror-tablespuppeteerreactreact-domreact-shadow-dom-retarget-eventsrehype-parserehype-rawrehype-sanitizerehype-stringifyremark-gfmremark-parseremark-rehypereplace-in-fileshelljsshxstyle-to-objecttabulator-tablestypescriptunifiedunist-util-visit
Lime Elements
In the ever-evolving landscape of web-applications, streamlining the creation of user interfaces (UIs) has become paramount. This is where web-component libraries and design systems come into play, offering a powerful combination to accelerate development, enhance consistency, and foster collaboration among developers.
Web-component libraries and design systems are crucial in the rapidly evolving web-applications landscape, accelerating development, enhancing consistency, and promoting collaboration.
Sponsored by Lime Technologies, Lime Elements is an open-source component library and a design system. It provides a high-quality set of well-designed, well-documented UI components, crafted in Stencil for enterprise-level products.
Our top developers and designers continuously improve Lime Elements, fixing bugs and adding new features. It serves as Lime Technologies' central repository for UI guidelines, standards, and components, ensuring a consistent brand experience across all our applications. Lime Elements standardizes colors, typography, layouts, and interactions for a cohesive, accessible user experience.
We invite you to leverage our web-component library and design system. It can streamline development, enhance consistency, ease collaboration, and deliver exceptional user experiences. Lime Elements can be instrumental in creating modern, scalable, and accessible web applications that resonate with users worldwide.
For a full list of components, along with live examples, please visit the documentation.
Getting Started
- To install, run
npm install @limetech/lime-elements.
Requirements
1. Font
To achieve a blazing fast rendering, our components' user interface utilizes a default cross-browser sans-serif font stack. As web components typically inherit font-related styles such as font-family, font-size, and color, we recommend defining these styles at a higher level, such as the <body> element. This is because we do not specify these defaults on each individual component.
To maintain consistency with the look & feel demonstrated in this documentation, we suggest incorporating the following styles into your project:
1font-family: ui-sans-serif, system-ui, sans-serif; 2font-size: 0.875rem; 3font-style: normal; 4font-weight: 400; 5color: rgb(var(--contrast-1500));
💡 About the color specified above, read more on our color system.
Feel free to customize the font-family and related styles to suit your project's needs. For example, you might prefer a different typeface like below:
1font-family: 'Roboto', Arial, Verdana, sans-serif;
2. Icons
At Lime, we utilize the Windows 10 icon set from Icons8. You may notice these icons in our components, such as the magnifying glass icon displayed as a leading icon on an input field.
If you're using Lime Elements in a non-Lime product, you'll need to provide your own icons. We're unable to redistribute Icons8's assets with our package due to licensing restrictions.
Providing your own icons is crucial as many of our components use an Icon interface. This interface allows you to specify an icon name, which corresponds to the filename of an SVG icon. For example, you can use this to display an icon on a button.
How to Set Up Your Icons Folder
-
For Lime products:
To use
@lundalogik/lime-icons8, the/assetsfolder from@lundalogik/lime-icons8must be made available on the web-server. -
For non-Lime products:
To use a different icon set, the icons must be placed in a folder structure that looks like this:
assets/icons/<name-of-icon>.svgIf
assetsis placed in the root, no other setup is needed. The icons will be fetched with a relative URL from/assets/icons/<name-of-icon>.svg.If
assetsis placed in a sub-folder somewhere, the easiest way to make the icons available is to use the HTMLbaseelement:1<base href="/my/parent/path/" />If this is not enough, or if the
baseelement is already in use for something else, a global icon path can be configured with thelimel-configelement:1<limel-config config={{iconPath: '/my/parent/path/'}} />
Using @beta components
Components marked as @beta are not yet stable. Here's what you need to know:
- Breaking changes: We may change
@betacomponents in ways that break your code. We won't increase the major version number when we do this. - Unstable:
@betacomponents may have more bugs than other components. Use them at your own risk. - Feedback wanted: We offer
@betacomponents to get your input. Your feedback helps us improve them.
Remember: All components can change, but @beta components change more often and without warning.
Getting help
- If you have a general question, or are in need of support, please open a Question issue on GitHub.
Contributing
- To build and run the documentation locally on your machine, run
npm start. - To see what other scripts are available, run
npm run. - Please read our guidelines for contributers
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
all dependencies are pinned
Details
- Info: 11 out of 11 GitHub-owned GitHubAction dependencies pinned
- Info: 4 out of 4 third-party GitHubAction dependencies pinned
- Info: 6 out of 6 npmCommand dependencies pinned
Reason
license file detected
Details
- Info: project has a license file: LICENSE.txt:0
- Warn: project license file does not contain an FSF or OSI license.
Reason
SAST tool is not run on all commits -- score normalized to 9
Details
- Warn: 23 commits out of 24 are checked with a SAST tool
Reason
Found 9/15 approved changesets -- score normalized to 6
Reason
8 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-282f-qqgm-c34q
- Warn: Project is vulnerable to: GHSA-5v2h-r2cx-5xgj
- Warn: Project is vulnerable to: GHSA-rrrm-qjm4-v8hf
- Warn: Project is vulnerable to: GHSA-pq67-2wwv-3xjx
- Warn: Project is vulnerable to: GHSA-8cj5-5rvv-wf4v
- Warn: Project is vulnerable to: GHSA-w5p7-h5w8-2hfq
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Reason
branch protection is not maximal on development and all release branches
Details
- Warn: branch protection not enabled for branch 'dev'
- Info: 'allow deletion' disabled on branch 'main'
- Info: 'force pushes' disabled on branch 'main'
- Warn: 'branch protection settings apply to administrators' is disabled on branch 'main'
- Info: 'stale review dismissal' is required to merge on branch 'main'
- Warn: required approving review count is 1 on branch 'main'
- Info: codeowner review is required on branch 'main'
- Warn: 'last push approval' is disabled on branch 'main'
- Info: 'up-to-date branches' is required to merge on branch 'main'
- Info: status check found to merge onto on branch 'main'
- Info: PRs are required in order to make changes on branch 'main'
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/pr-checks.yml:61
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/publish-docs.yml:58
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/release.yml:63
- Warn: no topLevel permission defined: .github/workflows/cleanup.yml:1
- Warn: no topLevel permission defined: .github/workflows/create-backport-branch.yml:1
- Warn: no topLevel permission defined: .github/workflows/pr-checks.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish-docs.yml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release.yml:16
- Warn: no topLevel permission defined: .github/workflows/sonarcloud.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Score
5.4
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More