@evergis/react MIT 51 versions

@evergis/react

npm

В данном репозитории находятся специфичные (в отличии от `@evergis/uilib-gl`) для `Evergis Online`, но в целом переиспользуемые на других проектах, построенных на Evergis API, React-компоненты.

51

Versions

MIT

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

eldarmamedovmaximgritsenkoarfeoart5255alexanderbom

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	2026/05/29
phantom-deps	phantom-dep:uuid	AI (phantom-deps): Same pattern — declared dep used transitively or in config, not a security concern.	ai	2026/05/27
phantom-deps	phantom-dep:punycode	AI (phantom-deps): Stable false positive for this package's dependency structure.	ai	2026/05/27
phantom-deps	phantom-dep:react-is	AI (phantom-deps): Stable false positive for this package's dependency structure.	ai	2026/05/27
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	2026/05/27
phantom-deps	phantom-dep:mapbox-gl-draw	AI (phantom-deps): Stable false positive for this package's dependency structure.	ai	2026/05/27
phantom-deps	phantom-dep:@svgdotjs/svg.js	AI (phantom-deps): Stable false positive for this package's dependency structure.	ai	2026/05/27
phantom-deps	phantom-dep:styled-system	AI (phantom-deps): Stable false positive for this package's dependency structure.	ai	2026/05/27

Versions (showing 51 of 155)

Version	Deps	Published
3.1.94	30 / 27	2025-12-15
3.1.93	30 / 27	2025-12-14
3.1.92	28 / 27	2025-12-09
3.1.91	28 / 27	2025-12-07
3.1.90	28 / 27	2025-12-07
3.1.89	28 / 27	2025-12-05
3.1.88	28 / 27	2025-12-04
3.1.87	28 / 27	2025-12-04
3.1.86	28 / 27	2025-12-04
3.1.85	28 / 27	2025-12-03
3.1.84	28 / 27	2025-12-03
3.1.83	28 / 27	2025-12-03
3.1.82	28 / 27	2025-12-02
3.1.81	28 / 27	2025-12-02
3.1.80	28 / 27	2025-12-02
3.1.78	28 / 27	2025-12-01
3.1.77	28 / 27	2025-12-01
3.1.76	28 / 27	2025-11-28
3.1.75	28 / 27	2025-11-28
3.1.74	28 / 27	2025-11-27
3.1.73	28 / 27	2025-11-27
3.1.72	28 / 27	2025-11-26
3.1.71	28 / 27	2025-11-26
3.1.70	28 / 27	2025-11-26
3.1.69	28 / 27	2025-11-26
3.1.68	28 / 27	2025-11-25
3.1.67	26 / 27	2025-11-24
3.1.66	26 / 27	2025-11-21
3.1.65	26 / 27	2025-11-20
3.1.64	26 / 27	2025-11-20
3.1.63	26 / 27	2025-11-20
3.1.62	26 / 27	2025-11-20
3.1.61	26 / 27	2025-11-19
3.1.60	26 / 27	2025-11-19
3.1.59	26 / 27	2025-11-18
3.1.58	26 / 27	2025-11-18
3.1.57	26 / 27	2025-11-17
3.1.56	26 / 27	2025-11-16
3.1.55	26 / 27	2025-11-14
3.1.54	26 / 27	2025-11-14
3.1.53	26 / 27	2025-11-14
3.1.52	26 / 27	2025-11-14
3.1.51	26 / 27	2025-11-14
3.1.50	26 / 27	2025-11-12
3.1.49	26 / 27	2025-11-11
3.1.48	26 / 27	2025-11-10
3.1.47	26 / 27	2025-11-10
3.1.46	26 / 27	2025-11-10
3.1.42	24 / 27	2025-11-06
3.1.41	24 / 27	2025-11-05
3.1.40	24 / 27	2025-11-01

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.92

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v3.1.62

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.