Is Typed Chrome Webstore Api Safe?

Typed Chrome Webstore Api — Nerq Trust Score 48.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Typed Chrome Webstore Api 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 Typed Chrome Webstore Api safe?

Trust Score Breakdown — Typed Chrome Webstore Api has a Nerq Trust Score of 48.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Typed Chrome Webstore Api Privacy Report →

What is Typed Chrome Webstore Api's trust score?

Typed Chrome Webstore Api 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 Typed Chrome Webstore Api?

Typed Chrome Webstore Api'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 Typed Chrome Webstore Api and who maintains it?

Authorcardinalby
Categorynpm Packages
SourceN/A

Typed Chrome Webstore Api Across Platforms

Same developer/company in other registries:

cardinalby/content-disposition
58/100 · packagist
Memrise Audio Uploader
50/100 · firefox
Google Maps Extended Routes
50/100 · firefox

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

Typed Chrome Webstore Api vs react-library-boilerplate-for-npmTyped Chrome Webstore Api vs bindlerTyped Chrome Webstore Api vs @yassidev/nuxt-directus

Safety Guide: Typed Chrome Webstore Api

What is Typed Chrome Webstore Api?

Typed Chrome Webstore Api is a Node.js package — Typed Chrome Webstore API to upload/publish extensions.

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=typed-chrome-webstore-api

Key Safety Concerns for Node.js package

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

Measured Signals

Typed Chrome Webstore Api 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 Typed Chrome Webstore Api Safe?
typed-chrome-webstore-api 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 Typed Chrome Webstore Api's trust score?
typed-chrome-webstore-api: 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=typed-chrome-webstore-api
What are safer alternatives to Typed Chrome Webstore Api?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. typed-chrome-webstore-api scores 48.2/100.
Does Typed Chrome Webstore Api have known vulnerabilities?
Nerq checks Typed Chrome Webstore Api 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 Typed Chrome Webstore Api actively maintained?
Typed Chrome Webstore Api 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