@jctrans-materials/comps-vue2
JCtrans Search Component compatible with Vue 2.6+ and Vue 3
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:sass | AI (phantom-deps): sass is a build-time CSS preprocessor; not directly imported in JS is expected for this package type. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): Likely used indirectly via bundled output; phantom-dep heuristic false positive for bundled libs. | ai | |
| phantom-deps | phantom-dep:crypto-js | AI (phantom-deps): Likely used indirectly via bundled output; phantom-dep heuristic false positive for bundled libs. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): Likely used indirectly via bundled output; phantom-dep heuristic false positive for bundled libs. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.0.40 | 10 / 11 | |
| 1.0.39 | 6 / 9 | |
| 1.0.38 | 6 / 9 | |
| 1.0.37 | 6 / 9 | |
| 1.0.36 | 6 / 7 | |
| 1.0.35 | 6 / 7 | |
| 1.0.34 | 6 / 7 | |
| 1.0.33 | 6 / 7 | |
| 1.0.32 | 6 / 7 | |
| 1.0.31 | 6 / 7 | |
| 1.0.30 | 6 / 7 | |
| 1.0.29 | 6 / 7 | |
| 1.0.28 | 6 / 7 | |
| 1.0.27 | 6 / 7 | |
| 1.0.26 | 6 / 7 | |
| 1.0.25 | 6 / 7 | |
| 1.0.24 | 6 / 7 | |
| 1.0.23 | 6 / 7 | |
| 1.0.22 | 6 / 7 | |
| 1.0.21 | 6 / 7 | |
| 1.0.20 | 6 / 7 | |
| 1.0.19 | 6 / 7 | |
| 1.0.18 | 6 / 7 | |
| 1.0.17 | 6 / 7 | |
| 1.0.16 | 6 / 7 | |
| 1.0.15 | 6 / 7 | |
| 1.0.14 | 6 / 7 | |
| 1.0.13 | 6 / 7 | |
| 1.0.12 | 6 / 7 | |
| 1.0.11 | 6 / 7 | |
| 1.0.10 | 6 / 7 | |
| 1.0.9 | 6 / 7 | |
| 1.0.8 | 4 / 6 | |
| 1.0.7 | 4 / 6 | |
| 1.0.6 | 4 / 6 | |
| 1.0.5 | 4 / 6 | |
| 1.0.4 | 4 / 6 | |
| 1.0.3 | 4 / 6 | |
| 1.0.2 | 4 / 6 | |
| 1.0.1 | 4 / 6 | |
| 1.0.0 | 4 / 6 |
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.