@siberiacancode/reactuse
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/cjs/hooks/useMask/useMask.cjs | AI (source-diff): Minified build artifact for useMask hook; readable logic visible in sample, no malicious indicators. | ai |
Versions (showing 100 of 203)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 0 / 15 | |
| 1.0.7 | 0 / 15 | |
| 1.0.6 | 0 / 15 | |
| 1.0.5 | 0 / 15 | |
| 1.0.4 | 0 / 15 | |
| 1.0.3 | 0 / 15 | |
| 1.0.2 | 0 / 15 | |
| 1.0.1 | 0 / 15 | |
| 1.0.0 | 0 / 15 | |
| 0.3.48 | 0 / 15 | |
| 0.3.47 | 0 / 15 | |
| 0.3.45 | 0 / 15 | |
| 0.3.44 | 0 / 15 | |
| 0.3.43 | 0 / 15 | |
| 0.3.42 | 0 / 15 | |
| 0.3.41 | 0 / 15 | |
| 0.3.40 | 0 / 15 | |
| 0.3.39 | 0 / 15 | |
| 0.3.38 | 0 / 15 | |
| 0.3.37 | 0 / 15 | |
| 0.3.35 | 0 / 15 | |
| 0.3.34 | 0 / 15 | |
| 0.3.33 | 0 / 15 | |
| 0.3.32 | 0 / 15 | |
| 0.3.31 | 0 / 15 | |
| 0.3.30 | 0 / 15 | |
| 0.3.29 | 0 / 15 | |
| 0.3.28 | 1 / 15 | |
| 0.3.27 | 1 / 15 | |
| 0.3.26 | 1 / 16 | |
| 0.3.25 | 1 / 16 | |
| 0.3.24 | 1 / 16 | |
| 0.3.23 | 1 / 16 | |
| 0.3.22 | 1 / 16 | |
| 0.3.21 | 1 / 16 | |
| 0.3.20 | 1 / 16 | |
| 0.3.19 | 1 / 16 | |
| 0.3.18 | 1 / 16 | |
| 0.3.17 | 1 / 16 | |
| 0.3.15 | 1 / 16 | |
| 0.3.13 | 1 / 15 | |
| 0.3.12 | 1 / 15 | |
| 0.3.10 | 1 / 15 | |
| 0.3.9 | 1 / 15 | |
| 0.3.8 | 1 / 15 | |
| 0.3.7 | 1 / 15 | |
| 0.3.6 | 1 / 15 | |
| 0.3.5 | 1 / 15 | |
| 0.3.4 | 1 / 15 | |
| 0.3.3 | 1 / 15 | |
| 0.3.2 | 1 / 15 | |
| 0.3.1 | 1 / 15 | |
| 0.3.0 | 1 / 15 | |
| 0.2.35 | 1 / 15 | |
| 0.2.34 | 1 / 15 | |
| 0.2.33 | 1 / 15 | |
| 0.2.32 | 1 / 15 | |
| 0.2.31 | 1 / 15 | |
| 0.2.30 | 1 / 15 | |
| 0.2.29 | 1 / 15 | |
| 0.2.28 | 1 / 15 | |
| 0.2.27 | 1 / 15 | |
| 0.2.26 | 1 / 15 | |
| 0.2.25 | 1 / 15 | |
| 0.2.24 | 1 / 15 | |
| 0.2.23 | 1 / 15 | |
| 0.2.22 | 1 / 15 | |
| 0.2.21 | 1 / 15 | |
| 0.2.20 | 1 / 15 | |
| 0.2.19 | 1 / 15 | |
| 0.2.18 | 1 / 15 | |
| 0.2.17 | 1 / 15 | |
| 0.2.16 | 1 / 15 | |
| 0.2.15 | 1 / 15 | |
| 0.2.14 | 1 / 15 | |
| 0.2.13 | 1 / 15 | |
| 0.2.12 | 1 / 15 | |
| 0.2.11 | 1 / 15 | |
| 0.2.10 | 1 / 15 | |
| 0.2.9 | 1 / 15 | |
| 0.2.8 | 1 / 15 | |
| 0.2.7 | 1 / 15 | |
| 0.2.6 | 1 / 15 | |
| 0.2.5 | 1 / 15 | |
| 0.2.4 | 1 / 15 | |
| 0.2.3 | 1 / 15 | |
| 0.2.2 | 1 / 15 | |
| 0.2.1 | 1 / 15 | |
| 0.2.0 | 1 / 15 | |
| 0.1.1 | 1 / 15 | |
| 0.1.0 | 1 / 15 | |
| 0.0.118 | 1 / 15 | |
| 0.0.117 | 1 / 15 | |
| 0.0.116 | 1 / 15 | |
| 0.0.115 | 1 / 15 | |
| 0.0.114 | 1 / 15 | |
| 0.0.113 | 1 / 14 | |
| 0.0.112 | 1 / 13 | |
| 0.0.111 | 1 / 13 | |
| 0.0.110 | 1 / 13 |
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.