← Home

@overextended/fx-utils

npm Repository Homepage

WIP development tools when working with the Cfx platform.

5
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

thelindatlukewastaken

Keywords

fivemoverextendedfxutils

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): tsc-alias is a standard TS build tool, used in config not malicious code. ai
bogus-package bogus-package AI (bogus-package): Sparse metadata typical of small utility packages from trusted publisher. ai
dependencies unvetted-dep:tsc-alias AI (dependencies): tsc-alias is a well-known TypeScript path alias resolver; its use in a build tooling package is expected and legitimate. ai
phantom-deps phantom-dep:tsc-alias AI (phantom-deps): tsc-alias is used in build config rather than direct JS imports; this is normal for a TypeScript build tool package. ai

Versions (showing 5 of 5)

Version Deps Published
0.0.6 2 / 2
0.0.4 2 / 2
0.0.3 2 / 2
0.0.2 1 / 2
0.0.1 1 / 2

v0.0.4

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thelindat.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thelindat.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.1

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.