Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
ntp-time-sync
Advanced tools
Readme
Node.JS module to fetch the current time from NTP servers and returns offset information.
:information_source: NTP requires UDP which is not available in a browser context!
# using Yarn
$ yarn add ntp-time-sync
# using NPM
$ npm install ntp-time-sync
Consider using the library as a singleton, so that not every call to getTime
fires new NTP packages.
The library itself will manage minimum/maximum poll times.
Several requests to multiple NTP time servers are fired and the responses will be aggregated.
// ES6:
import { NtpTimeSync } from "ntp-time-sync";
// pre-ES6:
// const NtpTimeSync = require("ntp-time-sync").NtpTimeSync;
const timeSync = NtpTimeSync.getInstance();
// request 1
timeSync.getTime().then(function (result) {
console.log("current system time", new Date());
console.log("real time", result.now);
console.log("offset in milliseconds", result.offset);
})
// request 2, will use cached offset from previous request
timeSync.getTime().then(function (result) {
console.log("current system time", new Date());
console.log("real time", result.now);
console.log("offset in milliseconds", result.offset);
})
// ES2017 style
const result = await timeSync.getTime();
console.log("real time", result.now);
<ntpTimeSyncInstance>.getTime()
returns a Promise
object which will eventually be resolved with a object containing the following information:
Property | Description |
---|---|
now | Current NTP time ("real time") |
offset | Calculated offset between local system time and NTP time |
<ntpTimeSyncInstance>.now()
returns a Date
object containing the correct time for the moment when the function was called.
In contrast to getTime()
, which will return the correct time for the moment the Promise gets resolved.
You can pass custom options to the constructor of NtpTimeSync
or NtpTimeSync.getInstance(options)
.
These will be merged with the following defaults:
const defaultOptions = {
// list of NTP time servers, optionally including a port (defaults to 123)
servers: [
"0.pool.ntp.org",
"1.pool.ntp.org",
"2.pool.ntp.org",
"3.pool.ntp.org"
],
// required amount of valid samples in order to calculate the time
sampleCount: 8,
// amount of time in milliseconds to wait for a single NTP response
replyTimeout: 3000,
// defaults as of RFC5905
ntpDefaults: {
port: 123,
version: 4,
tolerance: 15e-6,
minPoll: 4,
maxPoll: 17,
maxDispersion: 16,
minDispersion: 0.005,
maxDistance: 1,
maxStratum: 16,
precision: -18,
referenceDate: new Date("Jan 01 1900 GMT")
}
};
FAQs
Fetches the current time from NTP servers and returns offset information
The npm package ntp-time-sync receives a total of 1,173 weekly downloads. As such, ntp-time-sync popularity was classified as popular.
We found that ntp-time-sync demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.