@lemonadejs/calendar
LemonadeJS reactive JavaScript calendar plugin
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@lemonadejs/modal | AI (dependencies): Sibling package in the same LemonadeJS ecosystem; consistent co-dependency across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with no provenance history; consistent across all 32 versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.9.3 | 3 / 0 | |
| 5.9.2 | 3 / 0 | |
| 5.9.1 | 3 / 0 | |
| 5.9.0 | 3 / 0 | |
| 5.8.4 | 3 / 0 | |
| 5.8.3 | 3 / 0 | |
| 5.8.2 | 3 / 0 | |
| 5.8.1 | 3 / 0 | |
| 5.8.0 | 3 / 0 | |
| 5.3.0 | 2 / 0 | |
| 5.2.1 | 2 / 0 | |
| 5.2.0 | 2 / 0 |
v5.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.