← Home

@vtx/ol-map

npm Repository Homepage

React components for Vortex

15
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

vortex-front-endyzqdimanwuyusongwenlingaoyueliuowenhuang

Keywords

reactreact-component

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Used in a named string-to-function utility; consistent pattern across versions of this package. ai
phantom-deps phantom-dep:qs AI (phantom-deps): qs is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai
phantom-deps phantom-dep:moment AI (phantom-deps): moment is a declared runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 15 of 15)

Version Deps Published
1.0.174 16 / 44
1.0.173 16 / 44
1.0.172 16 / 44
1.0.171 16 / 44
1.0.167 16 / 44
1.0.163 16 / 43
1.0.161 16 / 43
1.0.160 16 / 43
1.0.158 16 / 43
1.0.157 16 / 43
1.0.156 16 / 43
1.0.155 16 / 43
1.0.154 16 / 43
1.0.153 16 / 43
1.0.152 16 / 43

v1.0.174

1 finding
LOW No provenance attestation provenance

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

v1.0.173

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 → gaoyueliu (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (gaoyueliu) than the most recent previously approved version (songwenlin) on 2026-05-26, but gaoyueliu 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.

v1.0.172

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: gaoyueliu → songwenlin (on 2026-05-08, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (gaoyueliu) on 2026-05-08, 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.

v1.0.171

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: gaoyueliu → songwenlin (on 2026-05-06, known maintainer) provenance

This version was published by a different npm account (songwenlin) than the most recent previously approved version (gaoyueliu) on 2026-05-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.

v1.0.167

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.163

1 finding
LOW No provenance attestation provenance

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

v1.0.161

1 finding
LOW No provenance attestation provenance

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

v1.0.160

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.158

1 finding
LOW No provenance attestation provenance

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

v1.0.157

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.156

1 finding
LOW No provenance attestation provenance

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

v1.0.155

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.154

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.153

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.152

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.