Is Source Tracking Safe?

Source Tracking — Nerq Trust Score 86.8/100 (A grade). Based on analysis of 2 trust dimensions, it is considered safe to use. Last updated: 2026-04-07.

Yes, Source Tracking is safe to use. Source Tracking is a npm package with a Nerq Trust Score of 86.8/100 (A), based on 3 independent data dimensions. Recommended for production use. Security: 90/100. Popularity: 75/100. Data sourced from npm registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-04-07. Machine-readable data (JSON).

Is Source Tracking safe?

YES — Source Tracking has a Nerq Trust Score of 86.8/100 (A). It meets Nerq's trust threshold with strong signals across security, maintenance, and community adoption. Recommended for production use — review the full report below for specific considerations.

Security Analysis → Source Tracking Privacy Report →

What is Source Tracking's trust score?

Source Tracking has a Nerq Trust Score of 86.8/100, earning a A grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
75

What are the key security findings for Source Tracking?

Source Tracking's strongest signal is security at 90/100. No known vulnerabilities have been detected. It meets the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 75/100 — community adoption

What is Source Tracking and who maintains it?

Authordemianbrecht
Categorynpm Packages
SourceN/A

Similar Npm by Trust Score

@supabase/supabase-js (90)@supabase/storage-js (90)@supabase/realtime-js (90)@supabase/functions-js (90)@testing-library/react (90)
See all safest Npm →

Compare

Source Tracking vs @supabase/supabase-jsSource Tracking vs @supabase/storage-jsSource Tracking vs @supabase/realtime-js

Safety Guide: Source Tracking

What is Source Tracking?

Source Tracking is a Node.js package — API for tracking local and remote Salesforce metadata changes.

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=@salesforce/source-tracking

Key Safety Concerns for Node.js package

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

Trust Assessment

Source Tracking has a Nerq Trust Score of 87/100 (A) and meets Nerq trust threshold. This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Source Tracking Safe?
Yes, it is safe to use. @salesforce/source-tracking with a Nerq Trust Score of 86.8/100 (A). Strongest signal: security (90/100). Score based on Security (90/100), Popularity (75/100).
What is Source Tracking's trust score?
@salesforce/source-tracking: 86.8/100 (A). Score based on Security (90/100), Popularity (75/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=@salesforce/source-tracking
What are safer alternatives to Source Tracking?
In the npm Packages category, more Node.js packages are being analyzed — check back soon. @salesforce/source-tracking scores 86.8/100.
Does Source Tracking have known vulnerabilities?
Nerq checks Source Tracking 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 Source Tracking actively maintained?
Source Tracking 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