@solid-primitives/refs
Library of primitives, components and directives for SolidJS that help managing references to JSX elements.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:redis | AI (typosquat): Scoped package @solid-primitives/refs is a legitimate SolidJS utility; Levenshtein match to 'redis' is purely coincidental with no impersonation intent. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Scoped package @solid-primitives/refs is a legitimate SolidJS utility; Levenshtein match to 'rxjs' is purely coincidental with no impersonation intent. | ai | |
| dependencies | unvetted-dep:@solid-primitives/utils | AI (dependencies): @solid-primitives/utils is a sibling package from the same solidjs-community monorepo; stable trusted dependency for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.4 | 1 / 2 | |
| 1.1.3 | 1 / 2 | |
| 1.1.2 | 1 / 2 | |
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 |
v1.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (davedbase) than the most recent previously approved version (thetarnav.) on 2026-07-04, but davedbase is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.