@jctrans-materials/nuxt
Nuxt module for JCtrans UI components
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vue | AI (phantom-deps): vue is a peer/framework dep used by convention in Nuxt modules, not directly imported. | ai | |
| phantom-deps | phantom-dep:@nuxt/kit | AI (phantom-deps): Framework-scoped package loaded by Nuxt module convention, not direct import. | ai | |
| phantom-deps | phantom-dep:vue-router | AI (phantom-deps): vue-router is a peer/framework dep used by convention in Nuxt modules. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): nuxt prepare is the standard Nuxt module type-stub generation step; stable and benign for this package. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Scoped Nuxt module for JCtrans UI; not impersonating 'next'. Levenshtein match is incidental. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.40 | 7 / 2 | |
| 1.0.37 | 7 / 2 | |
| 1.0.24 | 6 / 2 | |
| 1.0.7 | 6 / 1 | |
| 1.0.6 | 6 / 1 | |
| 1.0.5 | 6 / 1 | |
| 1.0.2 | 5 / 1 | |
| 1.0.1 | 5 / 1 |
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
3 findingsScript: nuxt prepare
Package name '@jctrans-materials/nuxt' is 1 edit(s) away from popular package 'next'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.