@fullcalendar/core 6.1.22

FullCalendar v6 core package (v7 is current: install your framework's v7 package and import plugins from it, e.g. @fullcalendar/react/daygrid). FullCalendar core package for rendering a calendar

@fullcalendar/core@6.1.22 was published on 2026-10-16. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @fullcalendar/core versions · Permanent reference to 6.1.22 · Latest release

Package specifications

Version6.1.22
License declarationMIT
Published2026-10-16T02:25:54.538Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified size141.65 KiB
Minified + gzip43.60 KiB
Unpacked distribution size1846.19 KiB
Published file count417
Package typemodule
ES module entry./index.js
Default entry./index.cjs
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies1
Repository stars20730
Repository forks3712

Install @fullcalendar/core 6.1.22

npm install @fullcalendar/core@6.1.22
pnpm add @fullcalendar/core@6.1.22
yarn add @fullcalendar/core@6.1.22

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Maintained10/10 — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
SAST0/10 — no SAST tool detected
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Signed-Releases0/10 — Project has not signed or included provenance with any releases.
Fuzzing0/10 — project is not fuzzed

Evidence and freshness