@remember-web/primitive
Remember Web Primitive Components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@radix-ui/react-label | AI (phantom-deps): Declared runtime dep used in radix subpath export; phantom-dep heuristic misses subpath-scoped imports. | ai |
Versions (showing 51 of 61)
| Version | Deps | Published |
|---|---|---|
| 0.5.9 | 8 / 21 | |
| 0.5.8 | 9 / 21 | |
| 0.5.7 | 9 / 21 | |
| 0.5.6 | 9 / 21 | |
| 0.5.5 | 9 / 21 | |
| 0.5.4 | 9 / 21 | |
| 0.5.3 | 9 / 21 | |
| 0.5.2 | 9 / 21 | |
| 0.5.1 | 9 / 21 | |
| 0.5.0 | 9 / 21 | |
| 0.4.8 | 10 / 21 | |
| 0.4.7 | 10 / 21 | |
| 0.4.6 | 10 / 21 | |
| 0.4.4 | 10 / 21 | |
| 0.4.3 | 10 / 21 | |
| 0.4.2 | 10 / 21 | |
| 0.4.1 | 10 / 21 | |
| 0.4.0 | 10 / 21 | |
| 0.3.7 | 10 / 23 | |
| 0.3.6 | 10 / 23 | |
| 0.3.5 | 10 / 23 | |
| 0.3.4 | 10 / 23 | |
| 0.3.3 | 10 / 23 | |
| 0.3.2 | 10 / 23 | |
| 0.3.1 | 10 / 23 | |
| 0.3.0 | 10 / 22 | |
| 0.2.14 | 10 / 22 | |
| 0.2.13 | 10 / 22 | |
| 0.2.12 | 10 / 22 | |
| 0.2.11 | 10 / 22 | |
| 0.2.10 | 10 / 22 | |
| 0.2.9 | 10 / 22 | |
| 0.2.8 | 10 / 22 | |
| 0.2.7 | 10 / 22 | |
| 0.2.6 | 10 / 22 | |
| 0.2.5 | 10 / 22 | |
| 0.2.4 | 10 / 22 | |
| 0.2.3 | 10 / 22 | |
| 0.2.2 | 10 / 22 | |
| 0.2.0 | 10 / 22 | |
| 0.1.20 | 10 / 22 | |
| 0.1.19 | 10 / 24 | |
| 0.1.18 | 10 / 24 | |
| 0.1.17 | 10 / 24 | |
| 0.1.16 | 10 / 24 | |
| 0.1.15 | 10 / 24 | |
| 0.1.14 | 10 / 24 | |
| 0.1.13 | 10 / 24 | |
| 0.1.12 | 10 / 24 | |
| 0.1.11 | 10 / 24 | |
| 0.1.10 | 10 / 24 |
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.