@jctrans-materials/comps-vue3 ISC 41 versions

@jctrans-materials/comps-vue3

npm

## 组件清单

41

Versions

ISC

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tuantuandawang

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:js-md5	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:nanoid	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:qrcode	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:crypto-js	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:js-cookie	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:lodash-es	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:tailwindcss	AI (phantom-deps): Build-tool dependency; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:@floating-ui/dom	AI (phantom-deps): Config-referenced utility; stable pattern for this package.	ai	2026/05/23
phantom-deps	phantom-dep:@tailwindcss/vite	AI (phantom-deps): Build-tool dependency; stable pattern for this package.	ai	2026/05/23

Versions (showing 41 of 41)

Version	Deps	Published
1.0.40	11 / 15	2026-06-02
1.0.39	11 / 15	2026-05-09
1.0.38	11 / 15	2026-05-09
1.0.37	11 / 15	2026-04-28
1.0.36	11 / 13	2026-03-16
1.0.35	11 / 13	2026-03-13
1.0.34	11 / 13	2026-03-05
1.0.33	11 / 13	2026-02-26
1.0.32	11 / 13	2026-02-06
1.0.31	11 / 13	2026-02-05
1.0.30	11 / 13	2026-02-05
1.0.29	11 / 13	2026-02-04
1.0.28	11 / 13	2026-02-03
1.0.27	11 / 13	2026-02-03
1.0.26	11 / 13	2026-02-03
1.0.25	11 / 13	2026-02-03
1.0.24	11 / 13	2026-02-02
1.0.23	11 / 13	2026-01-30
1.0.22	11 / 13	2026-01-28
1.0.21	11 / 13	2026-01-28
1.0.20	11 / 13	2026-01-27
1.0.19	11 / 13	2026-01-27
1.0.18	11 / 13	2026-01-26
1.0.17	11 / 13	2026-01-23
1.0.16	11 / 13	2026-01-20
1.0.15	11 / 13	2026-01-19
1.0.14	11 / 13	2026-01-14
1.0.13	10 / 12	2026-01-13
1.0.12	10 / 12	2026-01-13
1.0.11	8 / 11	2026-01-09
1.0.10	8 / 11	2026-01-09
1.0.9	8 / 9	2026-01-09
1.0.8	3 / 7	2026-01-04
1.0.7	3 / 7	2026-01-04
1.0.6	3 / 7	2026-01-04
1.0.5	3 / 7	2025-12-31
1.0.4	3 / 7	2025-12-30
1.0.3	3 / 7	2025-12-30
1.0.2	3 / 7	2025-12-30
1.0.1	3 / 7	2025-12-29
1.0.0	3 / 7	2025-12-29

v1.0.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.26

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.