@evergis/react
В данном репозитории находятся специфичные (в отличии от `@evergis/uilib-gl`) для `Evergis Online`, но в целом переиспользуемые на других проектах, построенных на Evergis API, React-компоненты.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Long-established scoped org package; sparse metadata is a stable characteristic, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Same pattern — declared dep used transitively or in config, not a security concern. | ai | |
| phantom-deps | phantom-dep:punycode | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:react-is | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:wkt | AI (phantom-deps): Large UI library; deps referenced in config/type files but not directly imported is expected pattern. | ai | |
| phantom-deps | phantom-dep:mapbox-gl-draw | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:@svgdotjs/svg.js | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai | |
| phantom-deps | phantom-dep:styled-system | AI (phantom-deps): Stable false positive for this package's dependency structure. | ai |
Versions (showing 55 of 155)
| Version | Deps | Published |
|---|---|---|
| 3.1.101 | 30 / 27 | |
| 3.1.100 | 30 / 27 | |
| 3.1.96 | 30 / 27 | |
| 3.1.95 | 30 / 27 | |
| 3.1.94 | 30 / 27 | |
| 3.1.93 | 30 / 27 | |
| 3.1.92 | 28 / 27 | |
| 3.1.91 | 28 / 27 | |
| 3.1.90 | 28 / 27 | |
| 3.1.89 | 28 / 27 | |
| 3.1.88 | 28 / 27 | |
| 3.1.87 | 28 / 27 | |
| 3.1.86 | 28 / 27 | |
| 3.1.85 | 28 / 27 | |
| 3.1.84 | 28 / 27 | |
| 3.1.83 | 28 / 27 | |
| 3.1.82 | 28 / 27 | |
| 3.1.81 | 28 / 27 | |
| 3.1.80 | 28 / 27 | |
| 3.1.78 | 28 / 27 | |
| 3.1.77 | 28 / 27 | |
| 3.1.76 | 28 / 27 | |
| 3.1.75 | 28 / 27 | |
| 3.1.74 | 28 / 27 | |
| 3.1.73 | 28 / 27 | |
| 3.1.72 | 28 / 27 | |
| 3.1.71 | 28 / 27 | |
| 3.1.70 | 28 / 27 | |
| 3.1.69 | 28 / 27 | |
| 3.1.68 | 28 / 27 | |
| 3.1.67 | 26 / 27 | |
| 3.1.66 | 26 / 27 | |
| 3.1.65 | 26 / 27 | |
| 3.1.64 | 26 / 27 | |
| 3.1.63 | 26 / 27 | |
| 3.1.62 | 26 / 27 | |
| 3.1.61 | 26 / 27 | |
| 3.1.60 | 26 / 27 | |
| 3.1.59 | 26 / 27 | |
| 3.1.58 | 26 / 27 | |
| 3.1.57 | 26 / 27 | |
| 3.1.56 | 26 / 27 | |
| 3.1.55 | 26 / 27 | |
| 3.1.54 | 26 / 27 | |
| 3.1.53 | 26 / 27 | |
| 3.1.52 | 26 / 27 | |
| 3.1.51 | 26 / 27 | |
| 3.1.50 | 26 / 27 | |
| 3.1.49 | 26 / 27 | |
| 3.1.48 | 26 / 27 | |
| 3.1.47 | 26 / 27 | |
| 3.1.46 | 26 / 27 | |
| 3.1.42 | 24 / 27 | |
| 3.1.41 | 24 / 27 | |
| 3.1.40 | 24 / 27 |
v3.1.101
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2025-12-26, but alexanderbom 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.100
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alexanderbom) than the most recent previously approved version (arfeo) on 2025-12-24, but alexanderbom 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.