Is Angular Unsavedchanges Safe?

Angular Unsavedchanges — Nerq Trust Score 48.2/100 (D grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-07-22.

Exercise caution with Angular Unsavedchanges. Angular Unsavedchanges 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 Angular Unsavedchanges safe?

NO — USE WITH CAUTION — Angular Unsavedchanges 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 → Angular Unsavedchanges Privacy Report →

What is Angular Unsavedchanges's trust score?

Angular Unsavedchanges 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 Angular Unsavedchanges?

Angular Unsavedchanges'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 Angular Unsavedchanges and who maintains it?

Authorcdiaz
Categorynpm Packages
SourceN/A

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

Angular Unsavedchanges vs react-library-boilerplate-for-npmAngular Unsavedchanges vs bindlerAngular Unsavedchanges vs @yassidev/nuxt-directus

Safety Guide: Angular Unsavedchanges

What is Angular Unsavedchanges?

Angular Unsavedchanges is a Node.js package — AngularJS directive to warn user of unsaved changes when navigating away from a form..

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=angular-unsavedchanges

Key Safety Concerns for Node.js package

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

Trust Assessment

Angular Unsavedchanges 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 Angular Unsavedchanges Safe?
Exercise caution. angular-unsavedchanges 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 Angular Unsavedchanges's trust score?
angular-unsavedchanges: 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=angular-unsavedchanges
What are safer alternatives to Angular Unsavedchanges?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. angular-unsavedchanges scores 48.2/100.
Does Angular Unsavedchanges have known vulnerabilities?
Nerq checks Angular Unsavedchanges 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 Angular Unsavedchanges actively maintained?
Angular Unsavedchanges 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