← Home

@downforce/reactx

npm Repository Homepage

Awesome React UI Widgets

20
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

daniele.orlando

Keywords

ReactUI

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Small internal package; lack of Sigstore attestation is consistent across all versions and not a security risk here. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit dependency of TypeScript compilation; stable for this package. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): Framework-scoped type package loaded by TypeScript convention; expected for React libraries. ai
phantom-deps phantom-dep:@types/react-dom AI (phantom-deps): Framework-scoped type package loaded by TypeScript convention; expected for React libraries. ai
typosquat typosquat.levenshtein:react AI (typosquat): @downforce/reactx is a legitimate scoped package in the downforce.js ecosystem, not a typosquat of react. The name reflects 'React eXtended' within the @downforce namespace. ai

Versions (showing 20 of 20)

Version Deps Published
1.2.10 0 / 2
1.2.9 0 / 2
1.2.8 0 / 2
1.2.7 0 / 2
1.2.6 0 / 2
1.2.5 0 / 2
1.2.4 0 / 2
1.2.3 0 / 2
1.2.2 0 / 2
1.2.1 0 / 2
1.2.0 0 / 2
1.1.9 0 / 2
1.1.8 0 / 2
1.1.7 3 / 2
1.1.6 3 / 2
1.1.5 3 / 2
1.1.3 7 / 2
1.1.2 7 / 2
1.1.1 7 / 2
1.1.0 7 / 2

v1.2.10

1 finding
LOW No provenance attestation provenance

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

v1.2.9

1 finding
LOW No provenance attestation provenance

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

v1.2.8

1 finding
LOW No provenance attestation provenance

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

v1.2.7

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'react' typosquat

Package name '@downforce/reactx' is 1 edit(s) away from popular package 'react'.

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.

v1.2.6

1 finding
LOW No provenance attestation provenance

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

v1.2.5

1 finding
LOW No provenance attestation provenance

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

v1.2.4

1 finding
LOW No provenance attestation provenance

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

v1.2.3

1 finding
LOW No provenance attestation provenance

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

v1.2.2

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

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.

v1.1.9

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.

v1.1.8

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.

v1.1.7

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.

v1.1.5

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.

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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