Is Testing Safe?

Testing — Nerq Trust Score 67.5/100 (B- grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-03-30.

Use Testing with some caution. Testing is a Node.js package with a Nerq Trust Score of 67.5/100 (B-), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 30/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-30. Machine-readable data (JSON).

Is Testing safe?

CAUTION — Testing has a Nerq Trust Score of 67.5/100 (B-). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → {name} Privacy Report →

What is Testing's trust score?

Testing has a Nerq Trust Score of 67.5/100, earning a B- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
30

What are the key security findings for Testing?

Testing's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 30/100 — community adoption

What is Testing and who maintains it?

Authordavidfrontegg
Categorynpm
SourceN/A

Similar Npm by Trust Score

@gravity-ui/date-components (78)@iobroker/plugin-docker (78)@agnos-ui/core (78)@devextreme-generator/vue (78)@epilot/email-template-client (78)
See all safest Npm →

Safety Guide: Testing

What is Testing?

Testing is a Node.js package — E2E testing framework for FrontMCP servers - MCP client, auth mocks, Playwright integration.

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=@frontmcp/testing

Key Safety Concerns for Node.js packages

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

Trust Assessment

Testing has a Nerq Trust Score of 68/100 (B-) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Testing safe to use?
Use with some caution. @frontmcp/testing has a Nerq Trust Score of 67.5/100 (B-). Strongest signal: security (90/100). Score based on security (90/100), popularity (30/100).
What is Testing's trust score?
@frontmcp/testing: 67.5/100 (B-). Score based on: security (90/100), popularity (30/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@frontmcp/testing
What are safer alternatives to Testing?
In the npm category, more Node.js packages are being analyzed — check back soon. @frontmcp/testing scores 67.5/100.
Does Testing have known vulnerabilities?
Nerq checks Testing 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.
How actively maintained is Testing?
Testing has a trust score of 67.5/100 (B-). Below Nerq Verified threshold — conduct additional review.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.