@overextended/ox_core
A modern FiveM framework.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nativewrappers/server | AI (dependencies): Standard FiveM server native type wrappers; appropriate dependency for a FiveM framework package. | ai | |
| dependencies | unvetted-dep:mariadb | AI (dependencies): mariadb is a well-known database connector; its use is expected and appropriate for a FiveM server framework like ox_core. | ai | |
| dependencies | unvetted-dep:@overextended/ox_lib | AI (dependencies): ox_lib is the companion library from the same Overextended org; its inclusion is expected across all ox_core versions. | ai | |
| dependencies | unvetted-dep:@nativewrappers/fivem | AI (dependencies): Standard FiveM native type wrappers; appropriate dependency for a FiveM framework package. | ai | |
| phantom-deps | phantom-dep:@biomejs/biome | AI (phantom-deps): Biome is a formatting/linting tool miscategorized as a runtime dep; it's only referenced in config files. Packaging hygiene issue, not a security concern. | ai | |
| phantom-deps | phantom-dep:@nativewrappers/fivem | AI (phantom-deps): FiveM native wrappers are used as type references in a FiveM framework; not being directly imported at runtime is expected for type-only usage. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.5.14 | 5 / 7 | |
| 1.5.13 | 5 / 7 | |
| 1.5.12 | 5 / 7 | |
| 1.5.10 | 5 / 7 | |
| 1.5.1 | 4 / 8 | |
| 1.5.0 | 4 / 8 | |
| 1.4.0 | 4 / 8 | |
| 1.3.2 | 4 / 8 | |
| 1.3.1 | 4 / 8 | |
| 1.3.0 | 4 / 8 | |
| 1.2.2 | 3 / 8 | |
| 1.2.1 | 3 / 8 | |
| 1.2.0 | 3 / 8 | |
| 1.1.3 | 3 / 8 | |
| 1.1.2 | 3 / 8 | |
| 1.1.1 | 3 / 8 | |
| 1.1.0 | 3 / 8 | |
| 1.0.1 | 3 / 8 | |
| 1.0.0 | 3 / 8 |
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.