Is Asset Legacy Token Name Mapping Safe? — Trust Score: 54.4/100

According to Nerq's independent analysis of @exodus/asset-legacy-token-name-mapping, this uncategorized has a trust score of 54.4 out of 100, earning a D grade. With 0 stars on npm_full, it is below the recommended threshold of 70. Compliance: 100/100 across 52 jurisdictions. Data sourced from 13+ independent signals including GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-18. Machine-readable data (JSON).

@exodus/asset-legacy-token-name-mapping has a Nerq Trust Score of 54.4/100 (D). Not yet Nerq Verified (requires 70+). Its strongest signal is compliance (100/100). Compliance: 52 of 52 jurisdictions. Last verified: 2026-03-18.

Is Asset Legacy Token Name Mapping safe?

CAUTION — Asset Legacy Token Name Mapping has a Nerq Trust Score of 54.4/100 (D). 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.

54.4

out of 100

D uncategorized npm_full

Trust Assessment

Caution — @exodus/asset-legacy-token-name-mapping has below-average trust signals. There may be concerns around maintenance frequency, security practices, or ecosystem adoption. Proceed with care and conduct additional due diligence.

Trust Signal Breakdown

Compliance

100

Regulatory alignment. EU AI Act risk class: N/A.

Details

Author	GitHub Actions
Category	uncategorized
Stars	0
Source	https://www.npmjs.com/package/@exodus/asset-legacy-token-name-mapping

Regulatory Compliance

EU AI Act Risk Class	Not assessed
Compliance Score	100/100
Jurisdictions	Assessed across 52 jurisdictions

Community Reviews

No reviews yet. Be the first to review @exodus/asset-legacy-token-name-mapping.

What Is Asset Legacy Token Name Mapping?

Asset Legacy Token Name Mapping is a AI tool in the uncategorized category. Old legacy name mapping for custom token migration.

As of March 2026, Asset Legacy Token Name Mapping is available on npm_full, making it an emerging tool in the AI ecosystem. But popularity alone does not equal safety — which is why Nerq independently analyzes every tool across 13+ trust signals.

How Nerq Assesses Asset Legacy Token Name Mapping's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Asset Legacy Token Name Mapping performs in each:

Compliance (100/100): Asset Legacy Token Name Mapping is broadly compliant. Assessed against regulations in 52 jurisdictions including the EU AI Act, CCPA, and GDPR.

The overall Trust Score of 54.4/100 (D) reflects the weighted combination of these signals. This is below the Nerq Verified threshold of 70. We recommend additional due diligence before production deployment.

Who Should Use Asset Legacy Token Name Mapping?

Asset Legacy Token Name Mapping is designed for:

Developers and teams working with uncategorized tools
Organizations evaluating AI tools for their stack
Researchers exploring AI capabilities in this domain

Risk guidance: Asset Legacy Token Name Mapping is suitable for development and testing environments. Before production deployment, conduct a thorough review of its security posture, review the specific trust signals above, and consider whether a higher-scored alternative meets your requirements.

How to Verify Asset Legacy Token Name Mapping's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any AI tool:

Check the source code — Review the repository security policy, open issues, and recent commits for signs of active maintenance.
Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Asset Legacy Token Name Mapping's dependency tree.
Review permissions — Understand what access Asset Legacy Token Name Mapping requires. AI tools should follow the principle of least privilege.
Test in isolation — Run Asset Legacy Token Name Mapping in a sandboxed environment before granting access to production data or systems.
Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=@exodus/asset-legacy-token-name-mapping
Review the license — Confirm that Asset Legacy Token Name Mapping's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Asset Legacy Token Name Mapping

When evaluating whether Asset Legacy Token Name Mapping is safe, consider these category-specific risks:

Data handling

Understand how Asset Legacy Token Name Mapping processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Asset Legacy Token Name Mapping's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Asset Legacy Token Name Mapping. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Asset Legacy Token Name Mapping connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.

License and IP compliance

Verify that Asset Legacy Token Name Mapping's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Asset Legacy Token Name Mapping in violation of its license can expose your organization to legal liability.

Best Practices for Using Asset Legacy Token Name Mapping Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Asset Legacy Token Name Mapping while minimizing risk:

Conduct regular audits

Periodically review how Asset Legacy Token Name Mapping is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Asset Legacy Token Name Mapping and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

Grant Asset Legacy Token Name Mapping only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for security advisories

Subscribe to Asset Legacy Token Name Mapping's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Asset Legacy Token Name Mapping is used within your organization, including data handling guidelines and acceptable use cases.

When Should You Avoid Asset Legacy Token Name Mapping?

Even promising tools aren't right for every situation. Consider avoiding Asset Legacy Token Name Mapping in these scenarios:

Production environments handling sensitive customer data
Regulated industries (healthcare, finance, government) without additional compliance review
Mission-critical systems where downtime has significant business impact

For each scenario, evaluate whether Asset Legacy Token Name Mapping's trust score of 54.4/100 meets your organization's risk tolerance. We recommend running a manual security assessment alongside the automated Nerq score.

How Asset Legacy Token Name Mapping Compares to Industry Standards

Nerq indexes over 204,000 AI agents and tools across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Asset Legacy Token Name Mapping's score of 54.4/100 is near the category average of 62/100.

This places Asset Legacy Token Name Mapping in line with the typical uncategorized tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.

Trust Score History

Nerq continuously monitors Asset Legacy Token Name Mapping and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Asset Legacy Token Name Mapping's score is updated within 24 hours.

Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Asset Legacy Token Name Mapping's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=@exodus/asset-legacy-token-name-mapping&include=history

Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Asset Legacy Token Name Mapping are strengthening or weakening over time.

Key Takeaways

Asset Legacy Token Name Mapping has a Trust Score of 54.4/100 (D) and is not yet Nerq Verified.
Asset Legacy Token Name Mapping shows moderate trust signals. Conduct thorough due diligence before deploying to production environments.
Among uncategorized tools, Asset Legacy Token Name Mapping scores near the category average of 62/100, suggesting room for improvement relative to peers.
Always verify safety independently — use Nerq's Preflight API for automated, up-to-date trust checks before integration.

Frequently Asked Questions

Is @exodus/asset-legacy-token-name-mapping safe to use?

@exodus/asset-legacy-token-name-mapping has a Nerq Trust Score of 54.4/100, earning a D grade. Caution — @exodus/asset-legacy-token-name-mapping has below-average trust signals. There may be concerns around maintenance frequency, security practices, or ecosystem adoption. Proceed with care and conduct additional due diligence. Its strongest signal is compliance (100/100). It has not yet reached the Nerq Verified threshold of 70. Always review the full KYA report before using any AI agent in production.

What is @exodus/asset-legacy-token-name-mapping's trust score?

Nerq assigns @exodus/asset-legacy-token-name-mapping a trust score of 54.4 out of 100, with a grade of D. This score is computed from multiple dimensions including security, compliance, maintenance activity, documentation quality, and community adoption (0 stars). Compliance score: 100/100. Scores are updated daily based on the latest publicly available signals.

Are there safer alternatives to @exodus/asset-legacy-token-name-mapping?

In the uncategorized category, no higher-rated alternatives were found — this is among the top-rated agents. @exodus/asset-legacy-token-name-mapping scores 54.4/100. When choosing between agents, consider your specific requirements for security (N/A), maintenance activity (N/A), and documentation (N/A). Use Nerq's comparison tools or the KYA endpoint for detailed side-by-side analysis.

How often is Asset Legacy Token Name Mapping's safety score updated?

Nerq continuously monitors Asset Legacy Token Name Mapping and updates its trust score as new data becomes available. The system ingests signals from 13+ independent sources including GitHub, NVD (National Vulnerability Database), OSV.dev, OpenSSF Scorecard, and major package registries (npm, PyPI). When a new CVE is disclosed, a dependency is updated, or commit activity changes, the score adjusts automatically. For the most current score, query the Nerq API: GET nerq.ai/v1/preflight?target=@exodus/asset-legacy-token-name-mapping. The current assessment (54.4/100, D) was last verified on 2026-03-18.

Can I use Asset Legacy Token Name Mapping in a regulated environment?

Asset Legacy Token Name Mapping has not yet reached the Nerq Verified threshold of 70, which means additional due diligence is recommended for regulated environments. Nerq assesses compliance across 52 jurisdictions. Asset Legacy Token Name Mapping has a compliance score of 100/100. For organizations in regulated industries (healthcare, finance, government), we recommend combining the Nerq Trust Score with your internal security review process, vendor risk assessment, and legal compliance check before deployment.

Add This Badge to YOUR Project

Show users your project is trusted. Add this badge to your README:

[![Nerq Trust Score](https://nerq.ai/badge/@exodus/asset-legacy-token-name-mapping)](https://nerq.ai/safe/asset-legacy-token-name-mapping)

Click to copy. Works on GitHub, GitLab, and any markdown renderer.

Scan your project

pip install nerq && nerq scan

Scans all dependencies for trust scores and security issues.

Integrate trust checks

curl nerq.ai/v1/preflight?target=asset-legacy-token-name-mapping

API docs →

Improve this score

See recommendations →

Verify any agent

Browse uncategorized

All agents · MCP servers · Compare · Gateway

Related Safety Checks

Is Cursor safe? Is ChatGPT safe? Is Claude safe? Is Windsurf safe? Is Bolt safe? Is Cline safe? Is GitHub Copilot safe? Is Gemini safe? Is Ollama safe? Is LangChain safe? Is OpenAI safe? Is n8n safe? Is ComfyUI safe? Is CrewAI safe? Is AutoGPT safe? Is Devin safe? Is Continue safe? Is LlamaIndex safe? Is Hugging Face safe? Is Stable Diffusion safe?

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