@hypen-space/core
Hypen core - Platform-agnostic reactive UI runtime (types, state, router, events)
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 |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is standard wasm-bindgen generated glue code, not intentional obfuscation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI framework package; name similarity to 'cors' is coincidental, not impersonation. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.4.980 | 0 / 2 | |
| 0.4.956 | 0 / 2 | |
| 0.4.955 | 0 / 2 | |
| 0.4.954 | 0 / 2 | |
| 0.4.953 | 0 / 2 | |
| 0.4.952 | 0 / 2 | |
| 0.4.951 | 0 / 2 | |
| 0.4.950 | 0 / 2 | |
| 0.4.949 | 0 / 2 | |
| 0.4.948 | 0 / 2 | |
| 0.4.947 | 0 / 2 | |
| 0.4.946 | 0 / 2 | |
| 0.4.945 | 0 / 2 | |
| 0.4.943 | 0 / 2 | |
| 0.4.942 | 0 / 2 | |
| 0.4.941 | 0 / 2 | |
| 0.4.94 | 0 / 2 | |
| 0.4.92 | 0 / 2 | |
| 0.4.91 | 0 / 2 | |
| 0.4.84 | 0 / 2 | |
| 0.4.83 | 0 / 2 | |
| 0.4.82 | 0 / 2 | |
| 0.4.81 | 0 / 2 | |
| 0.4.46 | 0 / 2 | |
| 0.4.45 | 0 / 2 | |
| 0.4.44 | 0 / 2 | |
| 0.4.43 | 0 / 2 | |
| 0.4.42 | 0 / 2 | |
| 0.4.41 | 0 / 2 | |
| 0.4.40 | 0 / 2 | |
| 0.4.39 | 0 / 2 | |
| 0.4.38 | 0 / 2 | |
| 0.4.37 | 0 / 2 | |
| 0.4.36 | 0 / 2 | |
| 0.4.35 | 0 / 2 | |
| 0.4.3 | 0 / 2 | |
| 0.4.2 | 0 / 2 | |
| 0.4.1 | 0 / 2 | |
| 0.4.0 | 0 / 2 | |
| 0.3.12 | 0 / 2 | |
| 0.3.11 | 0 / 2 | |
| 0.3.10 | 0 / 2 | |
| 0.3.9 | 0 / 2 | |
| 0.3.8 | 0 / 2 | |
| 0.3.7 | 0 / 2 | |
| 0.3.5 | 0 / 2 | |
| 0.3.4 | 0 / 2 | |
| 0.3.3 | 0 / 2 | |
| 0.3.2 | 0 / 2 | |
| 0.3.1 | 0 / 2 | |
| 0.3.0 | 0 / 2 | |
| 0.2.12 | 0 / 2 | |
| 0.2.11 | 0 / 2 | |
| 0.2.10 | 0 / 2 | |
| 0.2.9 | 0 / 2 | |
| 0.2.8 | 0 / 2 | |
| 0.2.7 | 0 / 2 | |
| 0.2.5 | 0 / 2 | |
| 0.2.4 | 0 / 2 | |
| 0.2.3 | 0 / 2 | |
| 0.2.2 | 0 / 2 | |
| 0.2.1 | 0 / 2 | |
| 0.2.0 | 0 / 2 |
v0.4.954
2 findingsPackage name '@hypen-space/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.4.953
2 findingsPackage name '@hypen-space/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.4.952
2 findingsPackage name '@hypen-space/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.4.951
2 findingsPackage name '@hypen-space/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.4.950
2 findingsPackage name '@hypen-space/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.4.949
2 findingsPackage name '@hypen-space/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.4.948
2 findingsPackage name '@hypen-space/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.4.947
2 findingsPackage name '@hypen-space/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.4.946
2 findingsPackage name '@hypen-space/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.4.945
2 findingsPackage name '@hypen-space/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.4.943
2 findingsPackage name '@hypen-space/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.4.942
2 findingsPackage name '@hypen-space/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.4.941
2 findingsPackage name '@hypen-space/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.4.94
2 findingsPackage name '@hypen-space/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.4.92
2 findingsPackage name '@hypen-space/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.4.91
2 findingsPackage name '@hypen-space/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.4.84
2 findingsPackage name '@hypen-space/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.4.83
2 findingsPackage name '@hypen-space/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.4.82
2 findingsPackage name '@hypen-space/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.4.81
2 findingsPackage name '@hypen-space/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.4.46
2 findingsPackage name '@hypen-space/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.4.45
2 findingsPackage name '@hypen-space/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.4.44
2 findingsPackage name '@hypen-space/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.4.43
2 findingsPackage name '@hypen-space/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.4.42
2 findingsPackage name '@hypen-space/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.4.41
2 findingsPackage name '@hypen-space/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.4.40
2 findingsPackage name '@hypen-space/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.4.39
2 findingsPackage name '@hypen-space/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.4.38
2 findingsPackage name '@hypen-space/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.4.37
2 findingsPackage name '@hypen-space/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.4.36
2 findingsPackage name '@hypen-space/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.4.35
2 findingsPackage name '@hypen-space/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.4.3
2 findingsPackage name '@hypen-space/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.4.2
2 findingsPackage name '@hypen-space/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.4.1
2 findingsPackage name '@hypen-space/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.4.0
2 findingsPackage name '@hypen-space/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.3.12
2 findingsPackage name '@hypen-space/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.3.11
2 findingsPackage name '@hypen-space/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.3.10
2 findingsPackage name '@hypen-space/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.3.9
2 findingsPackage name '@hypen-space/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.3.8
2 findingsPackage name '@hypen-space/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.3.7
2 findingsPackage name '@hypen-space/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.3.5
2 findingsPackage name '@hypen-space/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.3.4
2 findingsPackage name '@hypen-space/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.3.3
2 findingsPackage name '@hypen-space/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.3.2
2 findingsPackage name '@hypen-space/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.3.1
2 findingsPackage name '@hypen-space/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.3.0
2 findingsPackage name '@hypen-space/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.2.12
2 findingsPackage name '@hypen-space/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.2.11
2 findingsPackage name '@hypen-space/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.2.10
2 findingsPackage name '@hypen-space/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.2.9
2 findingsPackage name '@hypen-space/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.2.8
2 findingsPackage name '@hypen-space/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.2.7
2 findingsPackage name '@hypen-space/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.2.5
2 findingsPackage name '@hypen-space/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.2.4
2 findingsPackage name '@hypen-space/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.2.3
2 findingsPackage name '@hypen-space/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.2.2
2 findingsPackage name '@hypen-space/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.2.1
2 findingsPackage name '@hypen-space/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.2.0
2 findingsPackage name '@hypen-space/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.