react-datetime 3.0.1
A lightweight but complete datetime picker React.js component
react-datetime@3.0.1 was published on 2020-09-19. Its manifest declares 1 runtime dependency and 2 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All react-datetime versions · Permanent reference to 3.0.1 · Latest release
Package specifications
| Version | 3.0.1 |
|---|---|
| License declaration | MIT |
| Published | 2020-09-19T15:15:13.866Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 1 |
| Peer requirement count | 2 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 269.98 KiB |
| Published file count | 8 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | ./dist/react-datetime.cjs.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 5 |
| Repository stars | 2003 |
| Repository forks | 854 |
Install react-datetime 3.0.1
npm install react-datetime@3.0.1 pnpm add react-datetime@3.0.1 yarn add react-datetime@3.0.1
Runtime dependencies
- prop-types ^15.5.7
Peer requirements
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- js-tokens@4.0.0 — indirect
- loose-envify@1.4.0 — indirect
- object-assign@4.1.1 — indirect
- prop-types@15.8.1 — direct
- react-is@16.13.1 — indirect
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 4/10 — Found 8/20 approved changesets -- score normalized to 4 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/react-datetime/3.0.1 — retrieved 2026-10-29T18:48:09.340Z
- https://api.deps.dev/v3/projects/github.com%2Farqex%2Freact-datetime — retrieved 2026-10-29T18:21:51.155Z
- https://api.deps.dev/v3/systems/npm/packages/react-datetime/versions/3.0.1 — retrieved 2026-10-29T18:48:09.847Z
- https://api.deps.dev/v3/systems/npm/packages/react-datetime/versions/3.0.1:dependencies — retrieved 2026-10-29T18:48:09.877Z