Is Client Automation Safe?

Client Automation — Nerq Trust Score 78.2/100 (B+ grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-04-02.

Yes, Client Automation is safe to use. Client Automation is a Node.js package with a Nerq Trust Score of 78.2/100 (B+), based on 3 independent data dimensions. It is recommended for production use. Security: 90/100. Popularity: 60/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-02. Machine-readable data (JSON).

Is Client Automation safe?

YES — Client Automation has a Nerq Trust Score of 78.2/100 (B+). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → {name} Privacy Report →

What is Client Automation's trust score?

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

Security
90
Popularity
60

What are the key security findings for Client Automation?

Client Automation's strongest signal is security at 90/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

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

What is Client Automation and who maintains it?

Authordynatrace-nodejs
Categorynpm
SourceN/A

Similar Npm by Trust Score

canvas (88)langchain (88)@upstash/redis (88)tedious (88)postcss-reduce-initial (88)
See all safest Npm →

Compare

Client Automation vs canvasClient Automation vs langchainClient Automation vs @upstash/redis

Safety Guide: Client Automation

What is Client Automation?

Client Automation is a Node.js package — Automation API allows working with workflows and various trigger options..

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=@dynatrace-sdk/client-automation

Key Safety Concerns for Node.js packages

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

Trust Assessment

Client Automation has a Nerq Trust Score of 78/100 (B+) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Client Automation safe to use?
Yes, it is safe to use. @dynatrace-sdk/client-automation has a Nerq Trust Score of 78.2/100 (B+). Strongest signal: security (90/100). Score based on security (90/100), popularity (60/100).
What is Client Automation's trust score?
@dynatrace-sdk/client-automation: 78.2/100 (B+). Score based on: security (90/100), popularity (60/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@dynatrace-sdk/client-automation
What are safer alternatives to Client Automation?
In the npm category, more Node.js packages are being analyzed — check back soon. @dynatrace-sdk/client-automation scores 78.2/100.
Does Client Automation have known vulnerabilities?
Nerq checks Client Automation 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 Client Automation?
Client Automation has a trust score of 78.2/100 (B+). Meets Nerq Verified threshold.
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.

We use cookies for analytics and caching. Privacy Policy