@omegagrid/core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped datagrid package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 100 of 228)
| Version | Deps | Published |
|---|---|---|
| 0.10.44 | 7 / 11 | |
| 0.10.43 | 7 / 11 | |
| 0.10.42 | 7 / 11 | |
| 0.10.41 | 7 / 11 | |
| 0.10.40 | 7 / 11 | |
| 0.10.37 | 7 / 11 | |
| 0.10.36 | 7 / 11 | |
| 0.10.35 | 7 / 11 | |
| 0.10.34 | 7 / 11 | |
| 0.10.33 | 7 / 11 | |
| 0.10.32 | 7 / 11 | |
| 0.10.31 | 7 / 11 | |
| 0.10.30 | 7 / 11 | |
| 0.10.29 | 7 / 11 | |
| 0.10.28 | 7 / 11 | |
| 0.10.27 | 7 / 11 | |
| 0.10.26 | 7 / 11 | |
| 0.10.25 | 7 / 11 | |
| 0.10.24 | 7 / 11 | |
| 0.10.23 | 7 / 11 | |
| 0.10.22 | 7 / 11 | |
| 0.10.21 | 7 / 11 | |
| 0.10.20 | 7 / 11 | |
| 0.10.19 | 7 / 11 | |
| 0.10.18 | 7 / 11 | |
| 0.10.17 | 7 / 11 | |
| 0.10.16 | 7 / 11 | |
| 0.10.15 | 7 / 11 | |
| 0.10.14 | 7 / 11 | |
| 0.10.13 | 7 / 11 | |
| 0.10.12 | 7 / 11 | |
| 0.10.11 | 7 / 11 | |
| 0.10.10 | 7 / 11 | |
| 0.10.9 | 7 / 11 | |
| 0.10.8 | 7 / 11 | |
| 0.10.7 | 7 / 11 | |
| 0.10.6 | 7 / 11 | |
| 0.10.5 | 7 / 11 | |
| 0.10.4 | 7 / 11 | |
| 0.10.2 | 7 / 11 | |
| 0.10.1 | 7 / 11 | |
| 0.10.0 | 7 / 11 | |
| 0.9.59 | 7 / 11 | |
| 0.9.58 | 7 / 11 | |
| 0.9.57 | 7 / 11 | |
| 0.9.56 | 7 / 11 | |
| 0.9.55 | 7 / 11 | |
| 0.9.54 | 7 / 11 | |
| 0.9.53 | 7 / 11 | |
| 0.9.52 | 7 / 11 | |
| 0.9.51 | 7 / 11 | |
| 0.9.50 | 7 / 11 | |
| 0.9.49 | 7 / 11 | |
| 0.9.48 | 7 / 11 | |
| 0.9.47 | 7 / 11 | |
| 0.9.46 | 7 / 11 | |
| 0.9.45 | 7 / 11 | |
| 0.9.44 | 7 / 11 | |
| 0.9.43 | 7 / 11 | |
| 0.9.42 | 7 / 11 | |
| 0.9.41 | 7 / 11 | |
| 0.9.40 | 7 / 11 | |
| 0.9.39 | 7 / 11 | |
| 0.9.38 | 7 / 11 | |
| 0.9.37 | 7 / 11 | |
| 0.9.36 | 7 / 11 | |
| 0.9.35 | 7 / 11 | |
| 0.9.34 | 7 / 11 | |
| 0.9.33 | 7 / 11 | |
| 0.9.32 | 7 / 11 | |
| 0.9.31 | 7 / 11 | |
| 0.9.30 | 7 / 11 | |
| 0.9.29 | 7 / 11 | |
| 0.9.28 | 7 / 11 | |
| 0.9.27 | 7 / 11 | |
| 0.9.26 | 7 / 11 | |
| 0.9.25 | 7 / 11 | |
| 0.9.24 | 7 / 11 | |
| 0.9.23 | 7 / 11 | |
| 0.9.22 | 7 / 11 | |
| 0.9.21 | 7 / 11 | |
| 0.9.20 | 7 / 11 | |
| 0.9.19 | 7 / 11 | |
| 0.9.18 | 7 / 11 | |
| 0.9.17 | 7 / 11 | |
| 0.9.16 | 7 / 11 | |
| 0.9.15 | 7 / 11 | |
| 0.9.14 | 7 / 11 | |
| 0.9.13 | 7 / 11 | |
| 0.9.12 | 7 / 11 | |
| 0.9.11 | 7 / 11 | |
| 0.9.10 | 7 / 11 | |
| 0.9.9 | 7 / 11 | |
| 0.9.8 | 7 / 11 | |
| 0.9.7 | 7 / 11 | |
| 0.9.6 | 7 / 11 | |
| 0.9.5 | 7 / 11 | |
| 0.9.4 | 7 / 11 | |
| 0.9.3 | 7 / 11 | |
| 0.9.2 | 7 / 11 |
v0.10.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.36
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.35
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.34
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.33
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.32
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.31
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.30
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.29
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.28
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.27
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.26
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.25
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.24
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.23
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.22
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.21
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.19
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.18
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.14
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.13
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.12
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.11
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.10
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.59
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.58
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.57
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.56
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.55
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.54
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.53
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.52
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.51
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.50
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.49
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.48
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.47
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.46
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.45
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.44
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.43
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.42
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.41
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.40
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.39
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.38
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.37
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.36
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.35
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.34
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.33
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.32
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.31
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.30
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.29
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.28
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.27
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.26
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.25
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.24
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.23
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.22
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.21
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.20
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.19
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.18
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.17
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.16
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.15
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.14
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.13
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.11
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.9
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
2 findingsPackage name '@omegagrid/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.