Is Lime Web Components Interfaces Safe?

Lime Web Components Interfaces — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Lime Web Components Interfaces is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Last analyzed: 2026-03-25 Security: 90/100. Popularity: 0/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-25. Machine-readable data (JSON).

Is Lime Web Components Interfaces safe?

Trust Score Breakdown — Lime Web Components Interfaces has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Lime Web Components Interfaces Privacy Report →

What is Lime Web Components Interfaces's trust score?

Lime Web Components Interfaces has a Nerq Trust Score of 48.2/100, earning a D grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Lime Web Components Interfaces?

Lime Web Components Interfaces's strongest signal is security at 90/100. No known vulnerabilities have been detected.

✓Security score: 90/100 (strong)
⚠Popularity: 0/100 — community adoption

What is Lime Web Components Interfaces and who maintains it?

Authorspecularrain
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

react-library-boilerplate-for-npm (58)bindler (58)@yassidev/nuxt-directus (58)spectro-kubernetes-client (58)pocketto-svelte (58)
See all safest Npm →

Compare

Lime Web Components Interfaces vs react-library-boilerplate-for-npmLime Web Components Interfaces vs bindlerLime Web Components Interfaces vs @yassidev/nuxt-directus

Safety Guide: Lime Web Components Interfaces

What is Lime Web Components Interfaces?

Lime Web Components Interfaces is a Node.js package — **Has been deprecated! All code moved to `@limetech/lime-web-components`!**.

How to Verify Safety

Run npm audit to check for vulnerabilities. Review the package's GitHub repository for recent commits.

You can also check the trust score via API: GET /v1/preflight?target=@limetech/lime-web-components-interfaces

Key Safety Concerns for Node.js package

When evaluating any Node.js package, watch for: dependency vulnerabilities, malicious packages, typosquatting.

Measured Signals

Lime Web Components Interfaces has a Nerq Trust Score of 48/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Lime Web Components Interfaces Safe?
@limetech/lime-web-components-interfaces with a Nerq Trust Score of 48.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Lime Web Components Interfaces's trust score?
@limetech/lime-web-components-interfaces: 48.2/100 (D). Score based on Security (90/100), Popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@limetech/lime-web-components-interfaces
What are safer alternatives to Lime Web Components Interfaces?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @limetech/lime-web-components-interfaces scores 48.2/100.
Does Lime Web Components Interfaces have known vulnerabilities?
Nerq checks Lime Web Components Interfaces against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Lime Web Components Interfaces actively maintained?
Lime Web Components Interfaces maintenance score: N/A. Check the repository for recent commit activity and issue responsiveness.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy