← Home

@vtx/components

npm Repository Homepage

React components for Vortex

100
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

vortex-front-endyzqdimanwuyusongwenlingaoyueliuowenhuang

Keywords

reactreact-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): Raw IPs appear only in commented-out code; no runtime network call to those addresses. ai

Versions (showing 100 of 164)

Version Deps Published
3.1.190 26 / 42
3.1.188 26 / 42
3.1.187 24 / 42
3.1.186 24 / 42
3.1.185 24 / 42
3.1.172 25 / 41
3.1.171 25 / 41
3.1.170 25 / 41
3.1.169 25 / 41
3.1.168 25 / 41
3.1.167 25 / 41
3.1.155 25 / 41
3.1.154 25 / 41
3.1.153 25 / 41
3.1.152 25 / 41
3.1.150 25 / 41
3.1.149 25 / 41
3.1.148 25 / 41
3.1.147 25 / 41
3.1.146 25 / 41
3.1.145 25 / 41
3.1.144 25 / 41
3.1.143 25 / 41
3.1.142 25 / 41
3.1.141 25 / 41
3.1.140 25 / 41
3.1.139 25 / 41
3.1.138 25 / 41
3.1.137 25 / 41
3.1.136 25 / 41
3.1.135 25 / 41
3.1.134 25 / 41
3.1.133 25 / 41
3.1.132 25 / 41
3.1.131 25 / 41
3.1.130 25 / 41
3.1.129 25 / 41
3.1.128 25 / 41
3.1.127 25 / 41
3.1.126 25 / 41
3.1.125 25 / 41
3.1.124 25 / 41
3.1.123 25 / 41
3.1.122 25 / 41
3.1.121 25 / 41
3.1.120 25 / 41
3.1.119 25 / 41
3.1.118 25 / 41
3.1.117 25 / 41
3.1.116 25 / 41
3.1.115 25 / 41
3.1.114 25 / 41
3.1.113 24 / 41
3.1.112 24 / 41
3.1.111 24 / 41
3.1.109 24 / 41
3.1.108 24 / 41
3.1.107 24 / 41
3.1.106 24 / 41
3.1.105 24 / 41
3.1.104 24 / 41
3.1.103 24 / 41
3.1.102 24 / 41
3.1.101 24 / 41
3.1.100 24 / 41
3.1.99 24 / 41
3.1.98 24 / 41
3.1.97 24 / 41
3.1.96 24 / 41
3.1.95 24 / 41
3.1.94 24 / 41
3.1.93 24 / 41
3.1.92 24 / 41
3.1.91 24 / 41
3.1.90 24 / 41
3.1.89 24 / 41
3.1.88 24 / 41
3.1.86 24 / 41
3.1.85 24 / 41
3.1.84 24 / 41
3.1.83 24 / 41
3.1.81 24 / 41
3.1.80 24 / 41
3.1.79 24 / 41
3.1.78 24 / 41
3.1.77 23 / 41
3.1.76 23 / 41
3.1.75 23 / 41
3.1.74 23 / 41
3.1.73 23 / 41
3.1.72 23 / 41
3.1.71 23 / 41
3.1.70 23 / 41
3.1.69 23 / 41
3.1.68 23 / 41
3.1.67 23 / 41
3.1.66 23 / 41
3.1.65 23 / 41
3.1.64 23 / 41
3.1.63 23 / 41
Showing 100 of 164 Next page →

v3.1.147

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: manwuyu → vortex-front-end (on 2025-04-25, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (manwuyu) on 2025-04-25, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.146

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: manwuyu → vortex-front-end (on 2025-04-24, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (manwuyu) on 2025-04-24, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.145

1 finding
LOW No provenance attestation provenance

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

v3.1.144

1 finding
LOW No provenance attestation provenance

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

v3.1.143

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → manwuyu (on 2025-04-17, known maintainer) provenance

This version was published by a different npm account (manwuyu) than the most recent previously approved version (vortex-front-end) on 2025-04-17, but manwuyu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.142

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → manwuyu (on 2025-04-17, known maintainer) provenance

This version was published by a different npm account (manwuyu) than the most recent previously approved version (vortex-front-end) on 2025-04-17, but manwuyu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.141

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: manwuyu → vortex-front-end (on 2025-04-16, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (manwuyu) on 2025-04-16, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.140

1 finding
LOW No provenance attestation provenance

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

v3.1.139

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → manwuyu (on 2025-04-10, known maintainer) provenance

This version was published by a different npm account (manwuyu) than the most recent previously approved version (songwenlin) on 2025-04-10, but manwuyu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.138

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → manwuyu (on 2025-04-10, known maintainer) provenance

This version was published by a different npm account (manwuyu) than the most recent previously approved version (vortex-front-end) on 2025-04-10, but manwuyu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.137

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2025-04-02, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2025-04-02, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.136

1 finding
LOW No provenance attestation provenance

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

v3.1.135

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2025-03-26, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2025-03-26, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.134

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2025-03-25, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2025-03-25, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.133

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2025-03-20, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2025-03-20, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.132

1 finding
LOW No provenance attestation provenance

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

v3.1.131

1 finding
LOW No provenance attestation provenance

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

v3.1.130

1 finding
LOW No provenance attestation provenance

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

v3.1.129

1 finding
LOW No provenance attestation provenance

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

v3.1.128

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2025-02-25, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2025-02-25, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.127

1 finding
LOW No provenance attestation provenance

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

v3.1.126

1 finding
LOW No provenance attestation provenance

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

v3.1.125

1 finding
LOW No provenance attestation provenance

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

v3.1.124

1 finding
LOW No provenance attestation provenance

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

v3.1.123

1 finding
LOW No provenance attestation provenance

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

v3.1.122

1 finding
LOW No provenance attestation provenance

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

v3.1.121

1 finding
LOW No provenance attestation provenance

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

v3.1.120

1 finding
LOW No provenance attestation provenance

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

v3.1.119

1 finding
LOW No provenance attestation provenance

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

v3.1.118

1 finding
LOW No provenance attestation provenance

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

v3.1.117

1 finding
LOW No provenance attestation provenance

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

v3.1.116

1 finding
LOW No provenance attestation provenance

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

v3.1.115

1 finding
LOW No provenance attestation provenance

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

v3.1.114

1 finding
LOW No provenance attestation provenance

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

v3.1.113

1 finding
LOW No provenance attestation provenance

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

v3.1.112

1 finding
LOW No provenance attestation provenance

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

v3.1.111

1 finding
LOW No provenance attestation provenance

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

v3.1.109

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-12-27, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-12-27, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.108

1 finding
LOW No provenance attestation provenance

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

v3.1.107

1 finding
LOW No provenance attestation provenance

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

v3.1.106

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-12-23, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-12-23, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.105

1 finding
LOW No provenance attestation provenance

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

v3.1.104

1 finding
LOW No provenance attestation provenance

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

v3.1.103

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-12-12, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-12-12, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.102

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2024-12-11, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2024-12-11, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.101

1 finding
LOW No provenance attestation provenance

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

v3.1.100

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-12-11, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-12-11, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.99

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-12-11, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-12-11, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.98

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2024-12-06, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2024-12-06, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.97

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2024-12-04, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2024-12-04, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.96

1 finding
LOW No provenance attestation provenance

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

v3.1.95

1 finding
LOW No provenance attestation provenance

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

v3.1.94

1 finding
LOW No provenance attestation provenance

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

v3.1.93

1 finding
LOW No provenance attestation provenance

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

v3.1.92

1 finding
LOW No provenance attestation provenance

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

v3.1.91

1 finding
LOW No provenance attestation provenance

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

v3.1.90

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-09-27, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-09-27, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.89

1 finding
LOW No provenance attestation provenance

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

v3.1.88

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2024-09-07, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2024-09-07, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.86

1 finding
LOW No provenance attestation provenance

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

v3.1.85

1 finding
LOW No provenance attestation provenance

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

v3.1.84

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-08-06, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-08-06, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.83

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-08-05, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-08-05, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.81

1 finding
LOW No provenance attestation provenance

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

v3.1.80

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vortex-front-end → songwenlin (on 2024-07-02, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (vortex-front-end) on 2024-07-02, but songwenlin is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.79

1 finding
LOW No provenance attestation provenance

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

v3.1.78

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-07-02, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-07-02, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.77

1 finding
LOW No provenance attestation provenance

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

v3.1.76

1 finding
LOW No provenance attestation provenance

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

v3.1.75

1 finding
LOW No provenance attestation provenance

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

v3.1.74

1 finding
LOW No provenance attestation provenance

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

v3.1.73

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: songwenlin → vortex-front-end (on 2024-05-29, known maintainer) provenance

This version was published by a different npm account (vortex-front-end) than the most recent previously approved version (songwenlin) on 2024-05-29, but vortex-front-end is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.72

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.

v3.1.71

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.

v3.1.70

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.

v3.1.69

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.

v3.1.68

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.

v3.1.67

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.

v3.1.66

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.

v3.1.65

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.

v3.1.64

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.

v3.1.63

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.