Is Paffe Postpackager Map After Safe?

Paffe Postpackager Map After — Nerq Trust Score 46.2/100 (D grade). Score based on 2 independent trust signals. Last analyzed: 2026-03-25

Paffe Postpackager Map After is a npm package (paffe postpackager after map) with a Nerq Trust Score of 46.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 Paffe Postpackager Map After safe?

Trust Score Breakdown — Paffe Postpackager Map After has a Nerq Trust Score of 46.2/100 (D). Measured across 2 independent trust signals (as of 2026-03-25).

Security Analysis → Paffe Postpackager Map After Privacy Report →

What is Paffe Postpackager Map After's trust score?

Paffe Postpackager Map After has a Nerq Trust Score of 46.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 Paffe Postpackager Map After?

Paffe Postpackager Map After'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 Paffe Postpackager Map After and who maintains it?

Authorzhanghao
Categorynpm Packages
SourceN/A

Paffe Postpackager Map After Across Platforms

Same developer/company in other registries:

AddBookmarket
47/100 · pypi

Similar Npm by Trust Score

create-sss (56)sysdb (56)better-auth-lead (56)@typeserve/core (56)happy-translate (56)
See all safest Npm →

Compare

Paffe Postpackager Map After vs create-sssPaffe Postpackager Map After vs sysdbPaffe Postpackager Map After vs better-auth-lead

Safety Guide: Paffe Postpackager Map After

What is Paffe Postpackager Map After?

Paffe Postpackager Map After is a Node.js package — paffe postpackager after map.

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=paffe-postpackager-map-after

Key Safety Concerns for Node.js package

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

Measured Signals

Paffe Postpackager Map After has a Nerq Trust Score of 46/100 (D). This score is a composite of automated measurements of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Paffe Postpackager Map After Safe?
paffe-postpackager-map-after with a Nerq Trust Score of 46.2/100 (D). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (0/100).
What is Paffe Postpackager Map After's trust score?
paffe-postpackager-map-after: 46.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=paffe-postpackager-map-after
What are safer alternatives to Paffe Postpackager Map After?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. paffe-postpackager-map-after scores 46.2/100.
Does Paffe Postpackager Map After have known vulnerabilities?
Nerq checks Paffe Postpackager Map After 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 Paffe Postpackager Map After actively maintained?
Paffe Postpackager Map After 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