fix: update copyright information from Reflag ApS to Bucket ApS

- Changed copyright statements in LICENSE and various README files to reflect the new ownership by Bucket ApS.
- Updated references in the browser and node SDKs to ensure consistency with the new branding.
- Adjusted example files and documentation to align with the updated copyright information.

Author: pavkam

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2022 Reflag ApS
+Copyright (c) 2022 Bucket ApS
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

packages/browser-sdk/README.md

@@ -385,4 +385,4 @@ If you are including the Reflag tracking SDK with a `<script>`-tag from `jsdeliv
 ## License
 
 > MIT License
-> Copyright (c) 2025 Reflag ApS
+> Copyright (c) 2025 Bucket ApS

packages/browser-sdk/example/typescript/app.ts

@@ -21,6 +21,7 @@ const reflag = new ReflagClient({
 document
   .getElementById("startHuddle")
   ?.addEventListener("click", () => reflag.track(flagKey));
+
 document.getElementById("giveFeedback")?.addEventListener("click", (event) =>
   reflag.requestFeedback({
     flagKey,

packages/browser-sdk/src/flag/flagCache.ts

@@ -11,38 +11,35 @@ interface cacheEntry {
   flags: FetchedFlags;
 }
 
-// Parse and validate an API feature response
-export function parseAPIFeaturesResponse(
-  featuresInput: any,
-): FetchedFlags | undefined {
-  if (!isObject(featuresInput)) {
+// Parse and validate an API flag response
+export function parseAPIFlagsResponse(input: any): FetchedFlags | undefined {
+  if (!isObject(input)) {
     return;
   }
 
   const flags: FetchedFlags = {};
-  for (const key in featuresInput) {
-    const feature = featuresInput[key];
+  for (const key in input) {
+    const flag = input[key];
 
     if (
-      typeof feature.isEnabled !== "boolean" ||
-      feature.key !== key ||
-      typeof feature.targetingVersion !== "number" ||
-      (feature.config && typeof feature.config !== "object") ||
-      (feature.missingContextFields &&
-        !Array.isArray(feature.missingContextFields)) ||
-      (feature.ruleEvaluationResults &&
-        !Array.isArray(feature.ruleEvaluationResults))
+      typeof flag.isEnabled !== "boolean" ||
+      flag.key !== key ||
+      typeof flag.targetingVersion !== "number" ||
+      (flag.config && typeof flag.config !== "object") ||
+      (flag.missingContextFields &&
+        !Array.isArray(flag.missingContextFields)) ||
+      (flag.ruleEvaluationResults && !Array.isArray(flag.ruleEvaluationResults))
     ) {
       return;
     }
 
     flags[key] = {
-      isEnabled: feature.isEnabled,
-      targetingVersion: feature.targetingVersion,
+      isEnabled: flag.isEnabled,
+      targetingVersion: flag.targetingVersion,
       key,
-      config: feature.config,
-      missingContextFields: feature.missingContextFields,
-      ruleEvaluationResults: feature.ruleEvaluationResults,
+      config: flag.config,
+      missingContextFields: flag.missingContextFields,
+      ruleEvaluationResults: flag.ruleEvaluationResults,
     };
   }
 
@@ -144,7 +141,7 @@ function validateCacheData(cacheDataInput: any) {
     if (
       typeof cacheEntry.expireAt !== "number" ||
       typeof cacheEntry.staleAt !== "number" ||
-      (cacheEntry.flags && !parseAPIFeaturesResponse(cacheEntry.flags))
+      (cacheEntry.flags && !parseAPIFlagsResponse(cacheEntry.flags))
     ) {
       return;
     }

packages/browser-sdk/src/flag/flags.ts

@@ -3,7 +3,7 @@ import { HttpClient } from "../httpClient";
 import { Logger, loggerWithPrefix } from "../logger";
 import RateLimiter from "../rateLimiter";
 
-import { FlagCache, isObject, parseAPIFeaturesResponse } from "./flagCache";
+import { FlagCache, isObject, parseAPIFlagsResponse } from "./flagCache";
 
 /**
  * Represents a flag value.
@@ -126,7 +126,7 @@ export function validateFlagsResponse(response: any) {
     return;
   }
 
-  const flags = parseAPIFeaturesResponse(response.features);
+  const flags = parseAPIFlagsResponse(response.features);
 
   if (!flags) {
     return;

packages/browser-sdk/test/init.test.ts

@@ -40,7 +40,7 @@ describe("init", () => {
 
     server.use(
       http.get(
-        "https://example.com/features/evaluated",
+        "https://example.com/flags/evaluated",
         ({ request }: { request: StrictRequest<DefaultBodyType> }) => {
           usedSpecialHost = true;
           return getFlags({ request });

packages/cli/README.md

@@ -1,7 +1,7 @@
 # Reflag CLI
 
 Command-line interface for interacting with Reflag services. The CLI allows you to manage apps,
-features, authentication, and generate TypeScript types for your Reflag features. With this tool,
+flags, authentication, and generate TypeScript types for your Reflag flags. With this tool,
 you can streamline your feature flagging workflow directly from your terminal.
 
 ## Usage
@@ -17,7 +17,7 @@ yarn add --dev @reflag/cli
 ```
 
 Then running the `new` command from your project's root directory,
-initializing the CLI, creating a feature, and generating the types all at once:
+initializing the CLI, creating a flag, and generating the types all at once:
 
 ```bash
 # npm
@@ -35,19 +35,19 @@ Instead of running `new` you can call each step individually.
 # Initialize Reflag in your project (if not already setup)
 npx reflag init
 
-# Create a new feature
-npx reflag features create "My Feature"
+# Create a new flag
+npx reflag flags create "My new flag"
 
-# Generate TypeScript types for your features
-npx reflag features types
+# Generate TypeScript types for your flags
+npx reflag flags types
 ```
 
 ## Configuration
 
 The CLI creates a `reflag.config.json` file in your project directory when you run `reflag init`.
 This file contains all the necessary settings for your Reflag integration.
 
-### Configuration File Structure
+### Configuration file structure
 
 Here's a comprehensive list of configuration options available in the `reflag.config.json` file:
 
@@ -59,7 +59,7 @@ Here's a comprehensive list of configuration options available in the `reflag.co
   "appId": "ap123456789",
   "typesOutput": [
     {
-      "path": "gen/features.d.ts",
+      "path": "gen/flags.d.ts",
       "format": "react"
     }
   ]
@@ -72,7 +72,7 @@ Here's a comprehensive list of configuration options available in the `reflag.co
 | `baseUrl`     | Base URL for Reflag services.                                                                                                                                        | "https://app.bucket.co"                            |
 | `apiUrl`      | API URL for Reflag services (overrides baseUrl for API calls).                                                                                                       | "https://app.bucket.co/api"                        |
 | `appId`       | Your Reflag application ID.                                                                                                                                          | Required                                           |
-| `typesOutput` | Path(s) where TypeScript types will be generated. Can be a string or an array of objects with `path` and `format` properties. Available formats: `react` and `node`. | "gen/features.ts" with format "react"              |
+| `typesOutput` | Path(s) where TypeScript types will be generated. Can be a string or an array of objects with `path` and `format` properties. Available formats: `react` and `node`. | "gen/flags.ts" with format "react"                 |
 
 You can override these settings using command-line options for individual commands.
 
@@ -91,26 +91,26 @@ Options:
 
 - `--overwrite`: Overwrite existing configuration file if one exists.
 - `--app-id <id>`: Set the application ID.
-- `--key-format <format>`: Set the key format for features.
+- `--key-format <format>`: Set the key format for flags.
 
-### `reflag new [featureName]`
+### `reflag new [flagName]`
 
-All-in-one command to get started quickly. This command combines `init`, feature creation,
+All-in-one command to get started quickly. This command combines `init`, flag creation,
 and type generation in a single step. Use this for the fastest way to get up and running with Reflag.
 
 ```bash
-npx reflag new "My Feature" [--app-id ap123456789] [--key my-feature]  [--key-format custom] [--out gen/features.ts] [--format react]
+npx reflag new "My flag" [--app-id ap123456789] [--key my-flag]  [--key-format custom] [--out gen/flags.ts] [--format react]
 ```
 
 Options:
 
-- `--key`: Specific key for the feature.
+- `--key`: Specific key for the flag.
 - `--app-id`: App ID to use.
-- `--key-format`: Format for feature keys (custom, snake, camel, etc.).
+- `--key-format`: Format for flag keys (custom, snake, camel, etc.).
 - `--out`: Path to generate TypeScript types.
 - `--format`: Format of the generated types (react or node).
 
-If you prefer more control over each step, you can use the individual commands (`init`, `features create`, `features types`) instead.
+If you prefer more control over each step, you can use the individual commands (`init`, `flags create`, `flags types`) instead.
 
 ### `reflag login`
 
@@ -128,45 +128,45 @@ Log out from your Reflag account, removing stored credentials.
 npx reflag logout
 ```
 
-### `reflag features`
+### `reflag flags`
 
-Manage your Reflag features with the following subcommands.
+Manage your Reflag flags with the following subcommands.
 
-#### `reflag features create [featureName]`
+#### `reflag flags create [flagName]`
 
-Create a new feature in your Reflag app.
-The command guides you through the feature creation process with interactive prompts if options are not provided.
+Create a new flag in your Reflag app.
+The command guides you through the flag creation process with interactive prompts if options are not provided.
 
 ```bash
-npx reflag features create "My Feature" [--app-id ap123456789] [--key my-feature] [--key-format custom]
+npx reflag flags create "My flag" [--app-id ap123456789] [--key my-flag] [--key-format custom]
 ```
 
 Options:
 
-- `--key`: Specific key for the feature.
+- `--key`: Specific key for the flag.
 - `--app-id`: App ID to use.
-- `--key-format`: Format for feature keys.
+- `--key-format`: Format for flag keys.
 
-#### `reflag features list`
+#### `reflag flags list`
 
-List all features for the current app.
-This helps you visualize what features are available and their current configurations.
+List all flag for the current app.
+This helps you visualize what flags are available and their current configurations.
 
 ```bash
-npx reflag features list [--app-id ap123456789]
+npx reflag flags list [--app-id ap123456789]
 ```
 
 Options:
 
 - `--app-id`: App ID to use.
 
-#### `reflag features types`
+#### `reflag flags types`
 
-Generate TypeScript types for your features.
-This ensures type safety when using Reflag features in your TypeScript/JavaScript applications.
+Generate TypeScript types for your flags.
+This ensures type safety when using Reflag flags in your TypeScript/JavaScript applications.
 
 ```bash
-npx reflag features types [--app-id ap123456789] [--out gen/features.ts] [--format react]
+npx reflag flags types [--app-id ap123456789] [--out gen/flags.ts] [--format react]
 ```
 
 Options:
@@ -175,61 +175,6 @@ Options:
 - `--out`: Path to generate TypeScript types.
 - `--format`: Format of the generated types (react or node).
 
-### `reflag companies`
-
-Commands for managing companies.
-
-#### `reflag companies list`
-
-List all companies in your app.
-
-```bash
-npx reflag companies list [--filter <text>] [--app-id ap123456789]
-```
-
-Options:
-
-- `--filter`: Filter companies by name or ID.
-- `--app-id`: App ID to use.
-
-The command outputs a table with the following columns:
-
-- `id`: Company ID.
-- `name`: Company name (shows "(unnamed)" if not set).
-- `users`: Number of users in the company.
-- `lastSeen`: Date when the company was last active.
-
-### `reflag companies features access`
-
-Grant or revoke access to specific features for companies, segments, and users.
-If no feature key is provided, you'll be prompted to select one from a list.
-
-```bash
-npx reflag companies features access [--app-id ap123456789] [featureKey] [--enable|--disable] [--companies <id...>] [--segments <id...>] [--users <id...>]
-```
-
-Arguments:
-
-- `featureKey`: Key of the feature to grant/revoke access to (optional, interactive selection if omitted).
-
-Options:
-
-- `--enable`: Enable the feature for the specified targets.
-- `--disable`: Disable the feature for the specified targets.
-- `--users`: User IDs to target. Can be specified multiple times.
-- `--companies`: Company IDs to target. Can be specified multiple times.
-- `--segments`: Segment IDs to target. Can be specified multiple times.
-- `--app-id`: App ID to use.
-
-At least one target (companies, segments, or users) must be specified. You must also specify either `--enable` or `--disable`, but not both.
-
-Example:
-
-```bash
-# Enable feature for multiple companies and users
-npx reflag companies features access my-feature --enable --companies comp_123 --companies comp_456 --users user_789
-```
-
 ### `reflag apps`
 
 Commands for managing Reflag apps.
@@ -246,7 +191,7 @@ These options can be used with any command:
 
 ## AI-Assisted Development
 
-Reflag provides powerful AI-assisted development capabilities through rules and Model Context Protocol (MCP). These features help your AI development tools better understand your features and provide more accurate assistance.
+Reflag provides powerful AI-assisted development capabilities through rules and Model Context Protocol (MCP). These features help your AI development tools better understand your flags and provide more accurate assistance.
 
 ### Reflag Rules (Recommended)
 
@@ -267,7 +212,7 @@ This command will add rules to your project that provide AI tools with context a
 
 ## Model Context Protocol
 
-The Model Context Protocol (MCP) is an open protocol that provides a standardized way to connect AI models to different data sources and tools. In the context of Reflag, MCP enables your code editor to understand your feature flags, their states, and their relationships within your codebase. This creates a seamless bridge between your feature management workflow and AI-powered development tools. The MCP server is hosted by Reflag, so it's very easy to get started.
+The Model Context Protocol (MCP) is an open protocol that provides a standardized way to connect AI models to different data sources and tools. In the context of Reflag, MCP enables your code editor to understand your flags, their states, and their relationships within your codebase. This creates a seamless bridge between your feature management workflow and AI-powered development tools. The MCP server is hosted by Reflag, so it's very easy to get started.
 
 _\*\*Note: The Reflag `mcp` CLI command was previously used for a \_local_ server. However, in recent versions of the Reflag CLI, the `mcp` command has been repurposed to help you connect to the new remote MCP server.\*\*\_
 
@@ -321,11 +266,11 @@ Example CI workflow:
 ```yaml
 # GitHub Actions example
 - name: Generate types
-  run: npx reflag features types --api-key ${{ secrets.REFLAG_API_KEY }}
+  run: npx reflag flags types --api-key ${{ secrets.REFLAG_API_KEY }}
 
 # GitHub Actions example (using environment):
 - name: Generate types (environment)
-  run: npx reflag features types
+  run: npx reflag flags types
   env:
     REFLAG_API_KEY: ${{ secrets.REFLAG_CI_API_KEY }}
 ```
@@ -351,4 +296,4 @@ yarn format
 ## License
 
 > MIT License
-> Copyright (c) 2025 Reflag ApS
+> Copyright (c) 2025 Bucket ApS