
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-svelte
Advanced tools
PoC for a Svelte SDK for Unleash based on the official proxy-client-react.
The demo is part of this repo and is currently hosted on Vercel: https://proxy-client-svelte.vercel.app/
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-svelte
// or
yarn add @nunogois/proxy-client-svelte
Import the provider like this in your entrypoint file (typically index.svelte):
<script lang="ts">
let FlagProvider;
onMount(async () => {
const proxyClientSvelte = await import('@nunogois/proxy-client-svelte');
FlagProvider = proxyClientSvelte.default;
});
const config = {
url: 'https://HOSTNAME/proxy',
clientKey: 'PROXYKEY',
refreshInterval: 15,
appName: 'your-app-name',
environment: 'dev'
};
</script>
<svelte:component this="{FlagProvider}" {config}>
<App />
</svelte:component>
Alternatively, you can pass your own client in to the FlagProvider:
<script lang="ts">
import { UnleashClient } from '@nunogois/proxy-client-svelte';
let FlagProvider;
onMount(async () => {
const proxyClientSvelte = await import('@nunogois/proxy-client-svelte');
FlagProvider = proxyClientSvelte.default;
});
const config = {
url: 'https://HOSTNAME/proxy',
clientKey: 'PROXYKEY',
refreshInterval: 15,
appName: 'your-app-name',
environment: 'dev'
};
const client = new UnleashClient(config);
</script>
<svelte:component this="{FlagProvider}" unleashClient="{client}">
<App />
</svelte:component>
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 falseFlagProvider<svelte:component this="{FlagProvider}" unleashClient="{client}" startClient="{false}">
<App />
</svelte:component>
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.
<script lang="ts">
const client = new UnleashClient({
/* ... */
});
onMount(() => {
const asyncProcess = async () => {
// do async work ...
client.start();
};
asyncProcess();
});
</script>
<svelte:component this="{FlagProvider}" unleashClient="{client}" startClient="{false}">
<App />
</svelte:component>
To check if a feature is enabled:
<script lang="ts">
import { useFlag } from '@nunogois/proxy-client-svelte';
const enabled = useFlag('travel.landing');
</script>
{#if $enabled}
<SomeComponent />
{:else}
<AnotherComponent />
{/if}
To check variants:
<script lang="ts">
import { useVariant } from '@nunogois/proxy-client-svelte';
const variant = useVariant('travel.landing');
</script>
{#if $variant.enabled && $variant.name === 'SomeComponent'}
<SomeComponent />
{:else if $variant.enabled && $variant.name === 'AnotherComponent'}
<AnotherComponent />
{:else}
<DefaultComponent />
{/if}
useFlagsStatus retrieves the ready state and error events. Follow the following steps in order to delay rendering until the flags have been fetched.
<script lang="ts">
import { useFlagsStatus } from '@nunogois/proxy-client-svelte';
const { flagsReady, flagsError } = useFlagsStatus();
</script>
{#if !$flagsReady}
<Loading />
{:else}
<MyComponent error="{flagsError}" />
{/if}
Follow the following steps in order to update the unleash context:
<script lang="ts">
import { useUnleashContext, useFlag } from '@nunogois/proxy-client-svelte';
export let userId: string = undefined;
const updateContext = useUnleashContext();
onMount(() => {
updateContext({ userId });
});
$: {
async function run() {
await updateContext({ userId });
console.log('new flags loaded for', userId);
}
run();
}
</script>
FAQs
Svelte interface for working with Unleash
We found that @nunogois/proxy-client-svelte 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.