← Home

@effectify/react-remix

npm

Integration of Remix with Effect for React applications

19
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

andresdavidj

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:effect AI (phantom-deps): Declared dependency; referenced in config files for Effect integration. ai
phantom-deps phantom-dep:@remix-run/node AI (phantom-deps): Declared dependency; referenced in config files for Remix integration. ai
phantom-deps phantom-dep:@effect/platform AI (phantom-deps): Declared dependency; referenced in config files for Effect platform. ai
phantom-deps phantom-dep:@remix-run/react AI (phantom-deps): Declared dependency; referenced in config files for Remix React integration. ai
phantom-deps phantom-dep:@effect/platform-node AI (phantom-deps): Declared dependency; referenced in config files for Effect platform-node. ai
typosquat typosquat.levenshtein:react-redux AI (typosquat): Scoped @effectify package for Remix+Effect integration; name similarity to react-redux is coincidental, not impersonation. ai

Versions (showing 19 of 19)

Version Deps Published
0.5.11 0 / 5
0.5.10 0 / 5
0.5.9 0 / 5
0.5.8 0 / 5
0.5.7 0 / 5
0.5.6 0 / 5
0.5.5 0 / 5
0.5.4 5 / 0
0.5.3 5 / 0
0.5.2 5 / 0
0.5.1 5 / 0
0.5.0 5 / 0
0.4.7 5 / 0
0.4.6 5 / 0
0.4.5 5 / 0
0.4.1 5 / 0
0.3.0 5 / 0
0.2.0 5 / 0
0.1.0 5 / 0

v0.5.10

1 finding
LOW No provenance attestation provenance

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

v0.5.9

1 finding
LOW No provenance attestation provenance

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

v0.5.8

1 finding
LOW No provenance attestation provenance

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

v0.5.7

1 finding
LOW No provenance attestation provenance

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

v0.5.6

1 finding
LOW No provenance attestation provenance

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

v0.5.5

1 finding
LOW No provenance attestation provenance

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

v0.5.4

1 finding
LOW No provenance attestation provenance

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

v0.5.3

1 finding
LOW No provenance attestation provenance

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

v0.5.2

1 finding
LOW No provenance attestation provenance

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

v0.5.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.

v0.5.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.

v0.4.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.

v0.4.6

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.

v0.4.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.

v0.4.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.

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.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.