@fullcalendar/resource-daygrid
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@fullcalendar/premium-common | AI (dependencies): Same-org FullCalendar premium dependency; stable pattern across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): FullCalendar does not publish with Sigstore provenance; consistent across all versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.1.21 | 2 / 0 | |
| 6.1.20 | 2 / 0 | |
| 6.1.19 | 2 / 0 | |
| 6.1.18 | 2 / 0 | |
| 6.1.17 | 2 / 0 | |
| 6.1.15 | 2 / 0 | |
| 6.1.14 | 2 / 0 | |
| 6.1.13 | 2 / 0 | |
| 6.1.12 | 2 / 0 |
v6.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.