@intlayer/vue-compiler
Vite-compatible compiler plugin for Vue with Intlayer, providing HMR support, file transformation, and optimized dictionary loading for Vue 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/dictionaries-entry | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@intlayer/core | AI (phantom-deps): Same-org sibling at matching version; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:@intlayer/babel | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@intlayer/chokidar | AI (phantom-deps): Same-org sibling; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Peer dependency loaded by convention in build-tool context; stable for this package. | ai | |
| phantom-deps | phantom-dep:magic-string | AI (phantom-deps): Referenced in config files; standard build-tool usage pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver and link-dump README are expected patterns for intlayer monorepo packages synced at a shared version. | ai | |
| phantom-deps | phantom-dep:@intlayer/cli | AI (phantom-deps): Same-org sibling dep; declared in package.json as a runtime dependency, phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:fast-glob | AI (phantom-deps): fast-glob is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 115)
| Version | Deps | Published |
|---|---|---|
| 8.12.1 | 6 / 11 | |
| 8.12.0 | 6 / 11 | |
| 8.11.3 | 6 / 11 | |
| 8.11.2 | 6 / 11 | |
| 8.11.1 | 6 / 11 | |
| 8.11.0 | 6 / 11 | |
| 8.10.1 | 6 / 11 | |
| 8.10.0 | 6 / 11 | |
| 8.9.8 | 6 / 11 | |
| 8.9.7 | 6 / 11 | |
| 8.9.6 | 6 / 11 | |
| 8.9.5 | 6 / 11 | |
| 8.9.4 | 6 / 11 | |
| 8.9.3 | 6 / 11 | |
| 8.9.2 | 6 / 11 | |
| 8.9.1 | 6 / 11 | |
| 8.9.0 | 6 / 11 | |
| 8.8.0 | 6 / 11 | |
| 8.7.14 | 6 / 11 | |
| 8.7.13 | 6 / 11 | |
| 8.7.12 | 6 / 11 | |
| 8.7.11 | 6 / 11 | |
| 8.7.10 | 6 / 11 | |
| 8.7.9 | 6 / 11 | |
| 8.7.8 | 6 / 11 | |
| 8.7.7 | 6 / 11 | |
| 8.7.6 | 6 / 11 | |
| 8.7.5 | 6 / 11 | |
| 8.7.4 | 6 / 11 | |
| 8.7.3 | 6 / 11 | |
| 8.7.2 | 6 / 11 | |
| 8.7.1 | 6 / 11 | |
| 8.7.0 | 6 / 11 | |
| 8.6.10 | 6 / 11 | |
| 8.6.9 | 6 / 11 | |
| 8.6.8 | 6 / 11 | |
| 8.6.7 | 6 / 11 | |
| 8.6.6 | 6 / 11 | |
| 8.6.5 | 6 / 11 | |
| 8.6.4 | 6 / 11 | |
| 8.6.3 | 6 / 11 | |
| 8.6.2 | 6 / 11 | |
| 8.6.1 | 6 / 11 | |
| 8.6.0 | 6 / 11 | |
| 8.5.2 | 6 / 11 | |
| 8.5.1 | 6 / 11 | |
| 8.5.0 | 6 / 11 | |
| 8.4.10 | 6 / 11 | |
| 8.4.9 | 6 / 11 | |
| 8.4.8 | 6 / 11 | |
| 8.4.7 | 6 / 11 |
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.3
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.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.