@nativewrappers/server
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions as part of a legitimate CI/CD migration; backed by SLSA provenance attestation with Sigstore, confirming automated publishing from the official repo. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): @nativewrappers/server is a legitimate FiveM native wrapper library with 113 versions and SLSA provenance; the Levenshtein match to 'semver' is a false positive with no functional or namespace overlap. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() is used in a decorator initializer to read a property by name — standard decorator pattern, not obfuscation or evasion. | ai |
Versions (showing 97 of 97)
| Version | Deps | Published |
|---|---|---|
| 0.0.174 | 0 / 0 | |
| 0.0.173 | 0 / 0 | |
| 0.0.172 | 0 / 0 | |
| 0.0.171 | 0 / 0 | |
| 0.0.170 | 0 / 0 | |
| 0.0.169 | 0 / 0 | |
| 0.0.168 | 0 / 0 | |
| 0.0.167 | 0 / 0 | |
| 0.0.166 | 0 / 0 | |
| 0.0.165 | 0 / 0 | |
| 0.0.164 | 0 / 0 | |
| 0.0.163 | 0 / 0 | |
| 0.0.162 | 0 / 0 | |
| 0.0.161 | 0 / 0 | |
| 0.0.160 | 0 / 0 | |
| 0.0.159 | 0 / 0 | |
| 0.0.158 | 0 / 0 | |
| 0.0.157 | 0 / 0 | |
| 0.0.156 | 0 / 0 | |
| 0.0.148 | 0 / 0 | |
| 0.0.147 | 0 / 0 | |
| 0.0.146 | 0 / 0 | |
| 0.0.145 | 0 / 0 | |
| 0.0.144 | 0 / 0 | |
| 0.0.143 | 0 / 0 | |
| 0.0.142 | 0 / 0 | |
| 0.0.141 | 0 / 0 | |
| 0.0.140 | 0 / 0 | |
| 0.0.139 | 0 / 0 | |
| 0.0.138 | 0 / 0 | |
| 0.0.137 | 0 / 0 | |
| 0.0.136 | 0 / 0 | |
| 0.0.135 | 0 / 0 | |
| 0.0.134 | 0 / 0 | |
| 0.0.133 | 0 / 0 | |
| 0.0.132 | 0 / 0 | |
| 0.0.131 | 0 / 0 | |
| 0.0.130 | 0 / 0 | |
| 0.0.129 | 0 / 0 | |
| 0.0.128 | 0 / 0 | |
| 0.0.127 | 0 / 0 | |
| 0.0.126 | 0 / 0 | |
| 0.0.125 | 0 / 0 | |
| 0.0.124 | 0 / 0 | |
| 0.0.123 | 0 / 0 | |
| 0.0.122 | 0 / 0 | |
| 0.0.121 | 0 / 0 | |
| 0.0.120 | 0 / 0 | |
| 0.0.119 | 0 / 0 | |
| 0.0.118 | 0 / 0 | |
| 0.0.117 | 0 / 0 | |
| 0.0.116 | 0 / 0 | |
| 0.0.115 | 0 / 0 | |
| 0.0.114 | 0 / 0 | |
| 0.0.113 | 0 / 0 | |
| 0.0.112 | 0 / 0 | |
| 0.0.111 | 0 / 0 | |
| 0.0.110 | 0 / 0 | |
| 0.0.109 | 0 / 0 | |
| 0.0.108 | 0 / 0 | |
| 0.0.107 | 0 / 0 | |
| 0.0.106 | 0 / 0 | |
| 0.0.105 | 0 / 0 | |
| 0.0.104 | 0 / 0 | |
| 0.0.103 | 0 / 0 | |
| 0.0.102 | 0 / 0 | |
| 0.0.101 | 0 / 0 | |
| 0.0.100 | 0 / 0 | |
| 0.0.99 | 0 / 0 | |
| 0.0.98 | 0 / 0 | |
| 0.0.97 | 0 / 0 | |
| 0.0.96 | 0 / 0 | |
| 0.0.95 | 0 / 0 | |
| 0.0.94 | 0 / 0 | |
| 0.0.93 | 0 / 0 | |
| 0.0.92 | 0 / 0 | |
| 0.0.90 | 0 / 0 | |
| 0.0.89 | 0 / 0 | |
| 0.0.88 | 0 / 0 | |
| 0.0.87 | 0 / 0 | |
| 0.0.86 | 0 / 0 | |
| 0.0.85 | 0 / 0 | |
| 0.0.84 | 0 / 0 | |
| 0.0.83 | 0 / 0 | |
| 0.0.82 | 0 / 0 | |
| 0.0.81 | 0 / 0 | |
| 0.0.80 | 0 / 0 | |
| 0.0.79 | 0 / 0 | |
| 0.0.78 | 0 / 0 | |
| 0.0.77 | 0 / 0 | |
| 0.0.76 | 0 / 0 | |
| 0.0.75 | 0 / 0 | |
| 0.0.74 | 0 / 0 | |
| 0.0.73 | 0 / 0 | |
| 0.0.72 | 0 / 0 | |
| 0.0.65 | 1 / 0 | |
| 0.0.64 | 1 / 0 |
v0.0.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.