Is Clock Safe?

Clock — Nerq Trust Score 63.2/100 (C+ grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-04-07.

Use Clock with some caution. Clock is a PHP package with a Nerq Trust Score of 63.2/100 (C+), based on 3 independent data dimensions. Below the recommended threshold of 70. Security: 90/100. Popularity: 100/100. Data sourced from packagist.org, GitHub, and NVD. Last updated: 2026-04-07. Machine-readable data (JSON).

Is Clock safe?

CAUTION — Clock has a Nerq Trust Score of 63.2/100 (C+). 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.

Security Analysis → Clock Privacy Report →

What is Clock's trust score?

Clock has a Nerq Trust Score of 63.2/100, earning a C+ grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
100

What are the key security findings for Clock?

Clock's strongest signal is popularity at 100/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 100/100 — 428 stars on PHP Packages

What is Clock and who maintains it?

Authorsymfony
CategoryPHP Packages
Stars428
SourceN/A

Similar Packagist by Trust Score

geocoder-php/common-http (63)php-parallel-lint/php-console-color (63)driftingly/rector-laravel (63)queue-interop/queue-interop (63)laravel/serializable-closure (63)
See all safest Packagist →

Compare

Clock vs geocoder-php/common-httpClock vs php-parallel-lint/php-console-colorClock vs driftingly/rector-laravel

Safety Guide: Clock

What is Clock?

Clock is a PHP package — Decouples applications from the system clock.

How to Verify Safety

Run composer audit. Check packagist.org.

You can also check the trust score via API: GET /v1/preflight?target=symfony/clock

Key Safety Concerns for PHP package

When evaluating any PHP package, watch for: dependency vulnerabilities, PHP compatibility.

Trust Assessment

Clock has a Nerq Trust Score of 63/100 (C+) 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 Clock Safe?
Use with some caution. symfony/clock with a Nerq Trust Score of 63.2/100 (C+). Strongest signal: popularity (100/100). Score based on Security (90/100), Popularity (100/100).
What is Clock's trust score?
symfony/clock: 63.2/100 (C+). Score based on Security (90/100), Popularity (100/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=symfony/clock
What are safer alternatives to Clock?
In the PHP Packages category, more PHP packages are being analyzed — check back soon. symfony/clock scores 63.2/100.
Does Clock have known vulnerabilities?
Nerq checks Clock 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 Clock actively maintained?
Clock 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