NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev · #4836 most downloaded on pub.dev
A small, fast NTP (Network Time Protocol) client for Flutter and Dart with built-in offset caching.
Last release 4 months ago
25 May 2026
Too new to tell
only 2 release windows
Nearly every release is documented
notes for 3 of 3 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
3 releases · first in 2024
Fix: the cache was effectively never hit. The previous code stored the NTP offset as the cached value and later interpreted it as a microsecondsSinceE
microsecondsSinceEpoch for the "cached at" timestamp, so the freshness
check compared now() against a date near 1970 and always thought the
cache was stale. Cache now tracks (offset, syncedAt, server) correctly,
so subsequent now() calls are instant until the cache expires.encodeTimestamp overwrote array[7] with a random byte on every
call, corrupting the rootDelay field of the outgoing packet. The random
byte is now written to the last byte of the transmit timestamp as
RFC 5905 §3 suggests for spoofing resistance.ByteData (no more double-precision
arithmetic on 64-bit fixed-point timestamps), removing the subtle
precision loss from the previous pow(2.0, ...) decoder.NtpServer entries (ntpPool/pool,
milUsno/usno, etc.).FlutterNTP.sync() performs a one-shot round-trip and caches
the offset; new FlutterNTP.nowSync() returns the corrected time without
any I/O. FlutterNTP.now() keeps its old signature but gains
forceRefresh and allowFallback flags, plus optional server.NtpException instead of raw Strings.offset, lastSyncAt, lastSyncServer, and clearCache()
getters / utility.isSupported getter (returns false on the web).timeout.flutter_lints ^5.0.0, SDK constraints to Dart 3.4 /
Flutter 3.22.One column per month.
- README added.
- Initial release.
Your coding agent can read these notes before it upgrades. Set up the MCP server →