@dayflow/svelte
Svelte adapter for DayFlow calendar
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Low-risk Svelte adapter; no install scripts or malware indicators; provenance absence alone is not disqualifying. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Niche Svelte adapter with 28 versions; low-value signals reflect sparse metadata, not spam/phishing intent. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.6.4 | 0 / 15 | |
| 3.6.3 | 0 / 15 | |
| 3.6.2 | 0 / 15 | |
| 3.6.1 | 0 / 15 | |
| 3.6.0 | 0 / 15 | |
| 3.5.3 | 0 / 15 | |
| 3.5.2 | 0 / 15 | |
| 3.5.1 | 0 / 15 | |
| 3.5.0 | 0 / 15 | |
| 3.4.3 | 0 / 15 | |
| 3.4.2 | 0 / 15 | |
| 3.4.1 | 0 / 15 | |
| 3.4.0 | 0 / 15 | |
| 3.3.4 | 0 / 15 | |
| 3.3.3 | 0 / 15 | |
| 3.3.2 | 0 / 15 | |
| 3.2.3 | 0 / 15 | |
| 3.2.2 | 0 / 15 | |
| 3.2.0 | 0 / 15 | |
| 3.1.1 | 0 / 14 | |
| 3.1.0 | 0 / 14 | |
| 3.0.1 | 0 / 14 | |
| 3.0.0 | 0 / 14 |
v3.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jayceli.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.