@event-calendar/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped calendar package; name similarity to 'cors' is coincidental, not a squatting attempt. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is standard Proxy trap boilerplate in Svelte reactivity code; not obfuscation. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 5.7.1 | 1 / 0 | |
| 5.7.0 | 1 / 0 | |
| 5.6.1 | 1 / 0 | |
| 5.6.0 | 1 / 0 | |
| 5.5.1 | 1 / 0 | |
| 5.5.0 | 1 / 0 | |
| 5.4.2 | 1 / 0 | |
| 5.4.1 | 1 / 0 | |
| 5.4.0 | 1 / 0 | |
| 5.3.3 | 1 / 0 | |
| 5.3.2 | 1 / 0 | |
| 5.3.1 | 1 / 0 | |
| 5.3.0 | 1 / 0 | |
| 5.2.4 | 1 / 0 | |
| 5.2.3 | 1 / 0 | |
| 5.2.2 | 1 / 0 | |
| 5.2.1 | 1 / 0 | |
| 5.2.0 | 1 / 0 | |
| 5.1.4 | 1 / 0 | |
| 5.1.3 | 1 / 0 | |
| 5.1.2 | 1 / 0 | |
| 5.1.1 | 1 / 0 | |
| 5.1.0 | 1 / 0 | |
| 5.0.6 | 1 / 0 | |
| 5.0.5 | 1 / 0 | |
| 5.0.4 | 1 / 0 | |
| 5.0.3 | 1 / 0 | |
| 5.0.2 | 1 / 0 | |
| 5.0.1 | 1 / 0 | |
| 5.0.0 | 1 / 0 |
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.2
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
2 findingsPackage name '@event-calendar/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.