← Home

@fullcalendar/adaptive

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

arshaw

Keywords

calendareventfull-sizedfullcalendarschedulerresourceprint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established publisher; FullCalendar has never used Sigstore provenance across its 55 versions. ai
dependencies unvetted-dep:@fullcalendar/premium-common AI (dependencies): First-party sibling package from the same FullCalendar workspace and author; stable dependency relationship. ai

Versions (showing 3 of 3)

Version Deps Published
6.1.20 1 / 0
6.1.19 1 / 0
6.1.18 1 / 0

v6.1.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v6.1.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.