@saltcorn/filemanager
This is a project template for [Svelte](https://svelte.dev) apps. It lives at https://github.com/sveltejs/template.
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process use is in rollup.config.js dev build tooling only, not runtime package code. | ai | |
| phantom-deps | phantom-dep:sirv-cli | AI (phantom-deps): sirv-cli is referenced in the start script in package.json; phantom-dep heuristic fires because it's not directly imported in JS. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org package with 451 versions; metadata signals are false positives for this type of build artifact package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.5.7 | 1 / 11 | |
| 1.5.6 | 1 / 11 | |
| 1.5.5 | 1 / 11 | |
| 1.5.4 | 1 / 11 | |
| 1.5.3 | 1 / 11 | |
| 1.5.2 | 1 / 11 | |
| 1.5.0 | 1 / 11 | |
| 1.4.6 | 1 / 11 | |
| 1.4.5 | 1 / 11 | |
| 1.4.4 | 1 / 11 | |
| 1.4.3 | 1 / 11 | |
| 1.4.2 | 1 / 11 | |
| 1.4.1 | 1 / 11 | |
| 1.4.0 | 1 / 11 | |
| 1.3.1 | 1 / 11 | |
| 1.3.0 | 1 / 11 | |
| 1.2.0 | 1 / 11 |
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.