@jx3box/jx3box-ui
JX3BOX Vue3 UI
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:url | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:katex | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:jquery | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Known implicit runtime dep; stable false positive. | ai | |
| phantom-deps | phantom-dep:viewerjs | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:qrcode.vue | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:sortablejs | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:v-code-diff | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@vueuse/core | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:highlight.js | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:vuedraggable | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-data | AI (phantom-deps): Same-org dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:postcss-safe-parser | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-macro | AI (phantom-deps): Same-org dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@tinymce/tinymce-vue | AI (phantom-deps): Config-referenced dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-editor | AI (phantom-deps): Same-org dep in a Vue UI library; stable false positive. | ai | |
| phantom-deps | phantom-dep:@jx3box/jx3box-talent | AI (phantom-deps): Same-org dep in a Vue UI library; stable false positive. | ai |
Versions (showing 84 of 84)
| Version | Deps | Published |
|---|---|---|
| 2.2.20 | 29 / 27 | |
| 2.2.19 | 29 / 27 | |
| 2.2.18 | 29 / 27 | |
| 2.2.17 | 29 / 27 | |
| 2.2.16 | 29 / 27 | |
| 2.2.15 | 29 / 27 | |
| 2.2.14 | 29 / 27 | |
| 2.2.13 | 29 / 27 | |
| 2.2.12 | 29 / 27 | |
| 2.2.11 | 29 / 27 | |
| 2.2.10 | 29 / 27 | |
| 2.2.9 | 29 / 27 | |
| 2.2.8 | 29 / 27 | |
| 2.2.7 | 29 / 27 | |
| 2.2.6 | 29 / 27 | |
| 2.2.5 | 29 / 27 | |
| 2.2.4 | 29 / 27 | |
| 2.2.3 | 29 / 27 | |
| 2.2.2 | 29 / 27 | |
| 2.2.1 | 29 / 27 | |
| 2.2.0 | 29 / 27 | |
| 2.1.20 | 29 / 27 | |
| 2.1.19 | 29 / 27 | |
| 2.1.18 | 29 / 27 | |
| 2.1.17 | 29 / 27 | |
| 2.1.16 | 29 / 27 | |
| 2.1.15 | 29 / 27 | |
| 2.1.14 | 29 / 27 | |
| 2.1.13 | 29 / 27 | |
| 2.1.12 | 29 / 27 | |
| 2.1.11 | 29 / 27 | |
| 2.1.10 | 29 / 27 | |
| 2.1.9 | 29 / 27 | |
| 2.1.8 | 29 / 27 | |
| 2.1.7 | 29 / 27 | |
| 2.1.6 | 29 / 27 | |
| 2.1.5 | 29 / 27 | |
| 2.1.4 | 29 / 27 | |
| 2.1.3 | 29 / 27 | |
| 2.1.2 | 29 / 27 | |
| 2.1.1 | 29 / 27 | |
| 2.1.0 | 29 / 27 | |
| 2.0.42 | 29 / 27 | |
| 2.0.41 | 29 / 27 | |
| 2.0.40 | 29 / 27 | |
| 2.0.39 | 29 / 27 | |
| 2.0.38 | 29 / 27 | |
| 2.0.37 | 29 / 27 | |
| 2.0.36 | 29 / 27 | |
| 2.0.35 | 29 / 27 | |
| 2.0.34 | 29 / 27 | |
| 2.0.33 | 29 / 27 | |
| 2.0.32 | 29 / 27 | |
| 2.0.31 | 29 / 27 | |
| 2.0.30 | 29 / 27 | |
| 2.0.29 | 29 / 27 | |
| 2.0.28 | 29 / 27 | |
| 2.0.27 | 29 / 27 | |
| 2.0.26 | 29 / 27 | |
| 2.0.25 | 29 / 27 | |
| 2.0.24 | 25 / 31 | |
| 2.0.23 | 25 / 31 | |
| 2.0.22 | 25 / 31 | |
| 2.0.21 | 25 / 31 | |
| 2.0.20 | 25 / 31 | |
| 2.0.19 | 25 / 31 | |
| 2.0.18 | 25 / 31 | |
| 2.0.17 | 25 / 31 | |
| 2.0.16 | 25 / 31 | |
| 2.0.15 | 25 / 31 | |
| 2.0.12 | 25 / 31 | |
| 2.0.11 | 25 / 31 | |
| 2.0.10 | 25 / 31 | |
| 2.0.9 | 25 / 31 | |
| 2.0.8 | 25 / 31 | |
| 2.0.7 | 25 / 31 | |
| 2.0.6 | 25 / 31 | |
| 2.0.5 | 26 / 27 | |
| 2.0.4 | 26 / 22 | |
| 2.0.3 | 26 / 22 | |
| 2.0.2 | 26 / 22 | |
| 2.0.1 | 26 / 22 | |
| 2.0.0 | 26 / 22 | |
| 0.0.1 | 26 / 22 |
v2.2.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.