Is Parse Google Docs Json Safe?

Parse Google Docs Json — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-06-02.

Exercise caution with Parse Google Docs Json. Parse Google Docs Json is a npm package with a Nerq Trust Score of 48.2/100 (D), based on 3 independent data dimensions. Below the recommended threshold of 70. 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 Parse Google Docs Json safe?

NO — USE WITH CAUTION — Parse Google Docs Json has a Nerq Trust Score of 48.2/100 (D). It has below-average trust signals with significant gaps in security, maintenance, or documentation. Not recommended for production use without thorough manual review and additional security measures.

Security Analysis → Parse Google Docs Json Privacy Report →

What is Parse Google Docs Json's trust score?

Parse Google Docs Json 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 Parse Google Docs Json?

Parse Google Docs Json'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: 0/100 — community adoption

What is Parse Google Docs Json and who maintains it?

Authorfilipedeschamps
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

pulumi-improvmx (58)v3-jsoneditor (58)@khanglvm/llm-router (58)cypress-zephyr (58)@testpulse.run/reporter (58)
See all safest Npm →

Compare

Parse Google Docs Json vs pulumi-improvmxParse Google Docs Json vs v3-jsoneditorParse Google Docs Json vs @khanglvm/llm-router

Safety Guide: Parse Google Docs Json

What is Parse Google Docs Json?

Parse Google Docs Json is a Node.js package — This Node.js module authenticates with Google API and parse Google Docs to human-readable JSON or Markdown..

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=parse-google-docs-json

Key Safety Concerns for Node.js package

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

Trust Assessment

Parse Google Docs Json has a Nerq Trust Score of 48/100 (D) 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 Parse Google Docs Json Safe?
Exercise caution. parse-google-docs-json 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 Parse Google Docs Json's trust score?
parse-google-docs-json: 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=parse-google-docs-json
What are safer alternatives to Parse Google Docs Json?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. parse-google-docs-json scores 48.2/100.
Does Parse Google Docs Json have known vulnerabilities?
Nerq checks Parse Google Docs Json 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 Parse Google Docs Json actively maintained?
Parse Google Docs Json 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 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