
Security News
/Research
Fake Corepack Site Distributes Infostealer and Proxyware to Developers
A fake corepack.org site is impersonating the Node.js tool and delivers an infostealer and proxyware to developers who download it.
@nunogois/proxy-client-solid
Advanced tools
PoC for a Solid SDK for Unleash based on the official proxy-client-react.
This library is meant to be used with the unleash-proxy. The proxy application layer will sit between your unleash instance and your client applications, and provides performance and security benefits. DO NOT TRY to connect this library directly to the unleash instance, as the datasets follow different formats because the proxy only returns evaluated toggle information.
npm install @nunogois/proxy-client-solid
// or
yarn add @nunogois/proxy-client-solid
// or
pnpm i @nunogois/proxy-client-solid
Import the provider like this in your entrypoint file (typically index.jsx/tsx):
import { FlagProvider } from '@nunogois/proxy-client-solid'
const config = {
url: 'https://HOSTNAME/proxy',
clientKey: 'PROXYKEY',
refreshInterval: 15,
appName: 'your-app-name',
environment: 'dev'
}
render(
() => (
<FlagProvider config={config}>
<App />
</FlagProvider>
),
document.getElementById('root') as HTMLElement
)
Alternatively, you can pass your own client in to the FlagProvider:
import { FlagProvider, UnleashClient } from '@nunogois/proxy-client-solid'
const config = {
url: 'https://HOSTNAME/proxy',
clientKey: 'PROXYKEY',
refreshInterval: 15,
appName: 'your-app-name',
environment: 'dev'
}
const client = new UnleashClient(config)
render(
() => (
<FlagProvider unleashClient={client}>
<App />
</FlagProvider>
),
document.getElementById('root') as HTMLElement
)
By default, the Unleash client will start polling the Proxy for toggles immediately when the FlagProvider component renders. You can delay the polling by:
startClient prop to falseFlagProviderrender(
() => (
<FlagProvider unleashClient={client} startClient={false}>
<App />
</FlagProvider>
),
document.getElementById('root') as HTMLElement
)
Deferring the client start gives you more fine-grained control over when to start fetching the feature toggle configuration. This could be handy in cases where you need to get some other context data from the server before fetching toggles, for instance.
To start the client, use the client's start method. The below snippet of pseudocode will defer polling until the end of the asyncProcess function.
const client = new UnleashClient({
/* ... */
})
createEffect(() => {
const asyncProcess = async () => {
// do async work ...
client.start()
}
asyncProcess()
})
return (
// Pass client as `unleashClient` and set `startClient` to `false`
<FlagProvider unleashClient={client} startClient={false}>
<App />
</FlagProvider>
)
To check if a feature is enabled:
import { useFlag } from '@nunogois/proxy-client-solid'
const TestComponent = () => {
const enabled = useFlag('travel.landing')
if (enabled()) {
return <SomeComponent />
}
return <AnotherComponent />
}
export default TestComponent
To check variants:
import { useVariant } from '@nunogois/proxy-client-solid'
const TestComponent = () => {
const variant = useVariant('travel.landing')
if (variant().enabled && variant().name === 'SomeComponent') {
return <SomeComponent />
} else if (variant().enabled && variant().name === 'AnotherComponent') {
return <AnotherComponent />
}
return <DefaultComponent />
}
export default TestComponent
useFlagsStatus retrieves the ready state and error events. Follow the following steps in order to delay rendering until the flags have been fetched.
import { useFlagsStatus } from '@nunogois/proxy-client-solid'
const MyApp = () => {
const { flagsReady, flagsError } = useFlagsStatus()
if (!flagsReady()) {
return <Loading />
}
return <MyComponent error={flagsError()} />
}
Follow the following steps in order to update the unleash context:
import { useUnleashContext, useFlag } from '@nunogois/proxy-client-solid'
const MyComponent = ({ userId }) => {
const variant = useFlag('my-toggle')
const updateContext = useUnleashContext()
createEffect(() => {
// context is updated with userId
updateContext({ userId })
})
createEffect(() => {
async function run() {
// Can wait for the new flags to pull in from the different context
await updateContext({ userId })
console.log('new flags loaded for', userId)
}
run()
})
}
import { useUnleashContext, useUnleashClient } from '@nunogois/proxy-client-solid'
const MyComponent = ({ userId }) => {
const client = useUnleashClient();
const updateContext = useUnleashContext();
const login = () => {
// login user
if (client.isEnabled("new-onboarding")) {
// Send user to new onboarding flow
} else (
// send user to old onboarding flow
)
}
return <LoginForm login={login}/>
}
FAQs
Solid interface for working with Unleash
The npm package @nunogois/proxy-client-solid receives a total of 9 weekly downloads. As such, @nunogois/proxy-client-solid popularity was classified as not popular.
We found that @nunogois/proxy-client-solid demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
/Research
A fake corepack.org site is impersonating the Node.js tool and delivers an infostealer and proxyware to developers who download it.

Research
/Security News
A large-scale campaign abused GitHub Actions in compromised repositories to exploit CVE-2026-41940 in cPanel and WHM and steal server credentials.

Security News
Five frontier LLMs generated the same nonexistent package names, leaving 53 available for potential slopsquatting across PyPI and npm.