@aic-kits/remix
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redux | AI (typosquat): Scoped @aic-kits/remix package wraps @remix-run/react; no intent to impersonate redux. | ai | |
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Scoped @aic-kits/remix package wraps @remix-run/react; no intent to impersonate redis. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.39.1 | 1 / 11 | |
| 0.38.0 | 1 / 11 | |
| 0.37.0 | 1 / 11 | |
| 0.36.2 | 1 / 11 | |
| 0.36.0 | 1 / 11 | |
| 0.35.8 | 1 / 11 | |
| 0.35.6 | 1 / 11 | |
| 0.35.5 | 1 / 11 | |
| 0.35.4 | 1 / 11 | |
| 0.35.3 | 1 / 11 |
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.