@intlayer/svelte-compiler
Vite-compatible compiler plugin for Svelte with Intlayer, providing HMR support, file transformation, and optimized dictionary loading for Svelte applications.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@intlayer/core | AI (phantom-deps): Same-org monorepo dependency; loaded by convention. | ai | |
| phantom-deps | phantom-dep:@intlayer/dictionaries-entry | AI (phantom-deps): Same-org scoped dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@intlayer/babel | AI (phantom-deps): Same-org scoped dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@intlayer/chokidar | AI (phantom-deps): Same-org scoped dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped dependency loaded by convention in compiler plugin. | ai | |
| phantom-deps | phantom-dep:magic-string | AI (phantom-deps): Config-file reference; stable pattern for this compiler package. | ai | |
| phantom-deps | phantom-dep:@intlayer/cli | AI (phantom-deps): Same-org dep; phantom-dep heuristic false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): fast-glob is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 100 of 113)
| Version | Deps | Published |
|---|---|---|
| 8.12.1 | 4 / 13 | |
| 8.12.0 | 4 / 13 | |
| 8.11.3 | 4 / 13 | |
| 8.11.2 | 4 / 13 | |
| 8.11.1 | 4 / 13 | |
| 8.11.0 | 4 / 13 | |
| 8.10.1 | 4 / 13 | |
| 8.10.0 | 4 / 13 | |
| 8.9.8 | 4 / 13 | |
| 8.9.7 | 4 / 13 | |
| 8.9.6 | 4 / 13 | |
| 8.9.5 | 4 / 13 | |
| 8.9.4 | 4 / 13 | |
| 8.9.3 | 4 / 13 | |
| 8.9.2 | 4 / 13 | |
| 8.9.1 | 4 / 13 | |
| 8.9.0 | 4 / 13 | |
| 8.8.0 | 4 / 13 | |
| 8.7.14 | 4 / 13 | |
| 8.7.13 | 4 / 13 | |
| 8.7.12 | 4 / 13 | |
| 8.7.11 | 4 / 13 | |
| 8.7.10 | 4 / 13 | |
| 8.7.9 | 4 / 13 | |
| 8.7.8 | 4 / 13 | |
| 8.7.7 | 4 / 13 | |
| 8.7.6 | 4 / 13 | |
| 8.7.5 | 4 / 13 | |
| 8.7.4 | 4 / 13 | |
| 8.7.2 | 4 / 13 | |
| 8.7.1 | 4 / 13 | |
| 8.7.0 | 4 / 13 | |
| 8.6.10 | 4 / 13 | |
| 8.6.9 | 4 / 13 | |
| 8.6.8 | 4 / 13 | |
| 8.6.7 | 4 / 13 | |
| 8.6.6 | 4 / 13 | |
| 8.6.5 | 4 / 13 | |
| 8.6.4 | 4 / 13 | |
| 8.6.3 | 4 / 13 | |
| 8.6.2 | 4 / 13 | |
| 8.6.1 | 4 / 13 | |
| 8.6.0 | 4 / 13 | |
| 8.5.2 | 4 / 13 | |
| 8.5.1 | 4 / 13 | |
| 8.5.0 | 4 / 13 | |
| 8.4.10 | 4 / 13 | |
| 8.4.9 | 4 / 13 | |
| 8.4.8 | 4 / 13 | |
| 8.4.7 | 4 / 13 | |
| 8.4.6 | 4 / 13 | |
| 8.4.5 | 4 / 13 | |
| 8.4.4 | 4 / 13 | |
| 8.4.3 | 4 / 13 | |
| 8.4.2 | 4 / 13 | |
| 8.4.1 | 4 / 13 | |
| 8.4.0 | 4 / 13 | |
| 8.3.4 | 4 / 13 | |
| 8.3.3 | 4 / 13 | |
| 8.3.2 | 4 / 13 | |
| 8.3.1 | 4 / 13 | |
| 8.3.0 | 4 / 13 | |
| 8.2.4 | 3 / 11 | |
| 8.2.3 | 3 / 11 | |
| 8.2.2 | 3 / 11 | |
| 8.2.1 | 3 / 11 | |
| 8.2.0 | 3 / 11 | |
| 8.1.11 | 10 / 8 | |
| 8.1.10 | 10 / 8 | |
| 8.1.9 | 10 / 8 | |
| 8.1.7 | 10 / 8 | |
| 8.1.6 | 10 / 8 | |
| 8.1.5 | 10 / 8 | |
| 8.1.4 | 9 / 8 | |
| 8.1.3 | 9 / 8 | |
| 8.1.2 | 9 / 8 | |
| 8.1.1 | 9 / 8 | |
| 8.1.0 | 9 / 8 | |
| 8.0.5 | 9 / 8 | |
| 8.0.4 | 9 / 8 | |
| 8.0.2 | 9 / 8 | |
| 8.0.1 | 9 / 8 | |
| 8.0.0 | 9 / 8 | |
| 7.5.14 | 9 / 8 | |
| 7.5.13 | 9 / 8 | |
| 7.5.12 | 9 / 8 | |
| 7.5.11 | 9 / 8 | |
| 7.5.10 | 9 / 8 | |
| 7.5.9 | 9 / 8 | |
| 7.5.8 | 9 / 8 | |
| 7.5.7 | 9 / 8 | |
| 7.5.6 | 9 / 8 | |
| 7.5.5 | 9 / 8 | |
| 7.5.4 | 9 / 8 | |
| 7.5.3 | 9 / 8 | |
| 7.5.2 | 9 / 8 | |
| 7.5.1 | 9 / 8 | |
| 7.5.0 | 9 / 8 | |
| 7.4.0 | 9 / 8 | |
| 7.3.15 | 9 / 8 |
v8.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.