A clean, minimal template for building games with React, TypeScript, Three.js, and Vite - built with security-first principles.
Repo Hack23/game, read from GitHub 2 d ago. Hack23 has not joined Take My Repo.
Hack23/game is a public repo on GitHub by Hack23. A clean, minimal template for building games with React, TypeScript, Three.js, and Vite - built with security-first principles. It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it. It is written mainly in TypeScript, has 14 stars and last changed on 2026-11-06. It is archived: its maker no longer maintains it. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-21.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
A clean, minimal template for building games with React, TypeScript, Three.js, and Vite - built with security-first principles.
This template implements comprehensive security measures aligned with Hack23 AB's Information Security Management System (ISMS):
For complete security policy mapping and detailed compliance information, see:
typescript-7 alias and @typescript/typescript6The template is currently aligned with the following versions:
@typescript/typescript6This repository leverages GitHub Copilot's latest features for AI-assisted development:
Specialized AI experts for different development tasks:
Learn more: Custom Agents Documentation
Reusable patterns and best practices that agents automatically apply:
Learn more: Agent Skills Guide | Comprehensive Copilot Guide
When you create a new repository from this template, follow these essential setup steps to get all security and automation features working properly:
Labels are essential for automated pull request categorization and release note generation.
Run the setup workflow:
This creates all necessary labels for:
Enable GitHub Pages to automatically deploy your game when creating releases.
Setup GitHub Pages:
Your game will be automatically deployed to https://your-username.github.io/your-repo-name/ when you run the release workflow.
Update the OpenSSF Scorecard badge to point to your repository.
Edit the README:
[](https://scorecard.dev/viewer/?uri=github.com/your-username/your-repo-name)
Replace your-username/your-repo-name with your actual GitHub repository path.
With the template configured, you can now:
Develop locally or in Codespaces
npm install
npm run dev
Create pull requests - Labels will be automatically applied
Run tests - Automated testing on every push/PR
Create releases - Use the release workflow for deployment
Monitor security - Automated security scanning and scoring
Your repository includes these automated workflows:
| Workflow | Trigger | Purpose |
|---|---|---|
| Setup Repository Labels | Manual | Creates all required labels for PR categorization |
| Setup Copilot Environment | Manual | Validates and documents Copilot MCP server configuration |
| Test and Report | Push/PR | Runs unit tests, E2E tests, license compliance, SBOM quality validation, and generates coverage |
| Build, Attest and Release | Manual/Tag | Creates secure releases with SBOM, license validation, and attestations |
| CodeQL Analysis | Push/PR/Schedule | Static code analysis for security vulnerabilities |
| Dependency Review | PR | Reviews dependencies for known vulnerabilities |
| Scorecard Analysis | Push/Schedule | OSSF supply chain security assessment |
| ZAP Security Scan | Manual | Dynamic security testing of deployed app |
| Lighthouse Performance | Manual | Performance and accessibility audits |
Once configured, your repository automatically provides comprehensive security aligned with Hack23 AB's ISMS:
See ISMS Policy Mapping for complete feature-to-policy mapping.
src/components/ with your game logicpublic/assets/ directoryAll security workflows will protect your game from vulnerabilities while providing complete transparency through attestations and SBOM generation.
This template includes a fully configured development environment:
This repository is fully configured for GitHub Codespaces, providing:
This repository is configured with Model Context Protocol (MCP) servers that enhance GitHub Copilot's capabilities:
Configuration Files:
.github/copilot-instructions.md - Coding guidelines for Copilotdocs/MCP_CONFIGURATION.md - Detailed MCP setup documentationNote: MCP servers are automatically configured in the GitHub Codespaces environment and don't require separate configuration files.
Learn More: See MCP Configuration Guide for detailed setup and usage instructions.
The product-task-agent and GitHub MCP server require a Personal Access Token (PAT) to create and manage issues, access repository data, and perform other GitHub operations.
Generate a Fine-Grained Token (Recommended)
Go to GitHub Settings โ Developer settings โ Personal access tokens โ Fine-grained tokens
Click "Generate new token"
Fill in the details:
copilot-mcp-game (or your preferred name)Repository permissions (required):
Click "Generate token" and copy the token immediately (you won't see it again)
Alternative: Classic Token
repo (Full control of private repositories) - Requiredread:org (Read org membership) - Optionalworkflow (Update GitHub Actions workflows) - OptionalFor GitHub Codespaces:
GITHUB_TOKENThe token will be automatically available in your Codespace environment.
For Local Development:
# Linux/macOS - Add to ~/.bashrc or ~/.zshrc
export GITHUB_TOKEN="your_token_here"
# Windows PowerShell - Add to your PowerShell profile
$env:GITHUB_TOKEN="your_token_here"
# Windows Command Prompt
set GITHUB_TOKEN=your_token_here
Verify the token is set:
# In your terminal
echo $GITHUB_TOKEN # Linux/macOS
echo %GITHUB_TOKEN% # Windows CMD
echo $env:GITHUB_TOKEN # Windows PowerShell
| Permission | Access Level | Purpose |
|---|---|---|
| Issues | Read and write | Create and manage GitHub issues via product-task-agent |
| Contents | Read-only | Analyze code and repository structure |
| Metadata | Read-only | Access repository metadata (automatic) |
| Pull requests | Read and write | Manage PRs (optional) |
| Workflows | Read-only | Check workflow status (optional) |
Token not working:
GITHUB_TOKEN environment variable is set correctlyPermission errors when creating issues:
graph LR
A[Developer] -->|Opens in Codespace| B[Container Setup]
B -->|Auto-configures| C[Development Environment]
C -->|Provides| D[VS Code + Extensions]
C -->|Initializes| E[Node.js Environment]
C -->|Configures| F[Testing Tools]
D -->|Includes| G[GitHub Copilot]
D -->|Includes| H[ESLint Integration]
D -->|Includes| I[Debug Tools]
E -->|Installs| J[Three.js]
E -->|Installs| K[React 19]
E -->|Installs| L[TypeScript]
F -->|Prepares| M[Cypress E2E]
F -->|Prepares| N[Vitest Unit Tests]
G -->|Assists with| O[Game Logic]
G -->|Suggests| P[Game Components]
classDef primary fill:#e3f2fd,stroke:#1565c0,stroke-width:2px,color:#000
classDef tools fill:#e8f5e8,stroke:#2e7d32,stroke-width:2px,color:#000
classDef ai fill:#fff3e0,stroke:#e65100,stroke-width:2px,color:#000
classDef testing fill:#f3e5f5,stroke:#4a148c,stroke-width:2px,color:#000
class A,B,C primary
class D,E,F tools
class G,O,P ai
class M,N testing
class J,K,L tools
class H,I tools
graph TD
A[๐ Code Push/PR] --> B{๐ก๏ธ Security Gates}
B --> |๐ Code Analysis| C[CodeQL Scanning]
B --> |๐ฆ Dependencies| D[Dependency Review]
B --> |๐ License Check| E[License Compliance]
B --> |๐๏ธ Supply Chain| F[OSSF Scorecard]
C --> |๐จ Vulnerabilities| G[Security Alerts]
D --> |โ ๏ธ Known CVEs| G
E --> |๏ฟฝ Invalid Licenses| G
F --> |๏ฟฝ๐ Security Score| H[Security Dashboard]
G --> I[๐ซ Block Merge]
H --> J[โ
Security Badge]
subgraph "๐ Protection Layers"
K[Runner Hardening]
L[Pinned Actions]
M[Audit Logging]
end
subgraph "๐งช Runtime Security Testing"
N[๐ท๏ธ ZAP DAST Scan]
O[โก Lighthouse Audit]
P[๐ Live Site Testing]
end
J --> N
N --> |๐ Dynamic Scan| O
O --> |๐ Performance Report| P
%% Styling
classDef security fill:#ffebee,stroke:#c62828,stroke-width:2px,color:#000
classDef analysis fill:#e8f5e8,stroke:#2e7d32,stroke-width:2px,color:#000
classDef protection fill:#e3f2fd,stroke:#1565c0,stroke-width:2px,color:#000
classDef alert fill:#fff3e0,stroke:#ef6c00,stroke-width:2px,color:#000
classDef runtime fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px,color:#000
class A,B,I security
class C,D,E,F analysis
class K,L,M protection
class G,H,J alert
class N,O,P runtime
graph TD
A[๐ Code Push/PR] --> B{๐ Prepare Environment}
B --> |โ
Dependencies| C[๐๏ธ Build Validation]
B --> |โ
Cypress Cache| D[๐งช Unit Tests]
B --> |โ
Display Setup| E[๐ E2E Tests]
C --> |โ
Build Success| F{๐ Parallel Testing}
F --> D
F --> E
D --> |๐ Coverage Report| G[๐ Test Reports]
E --> |๐ฌ Videos & Screenshots| G
G --> H[๐ค Artifact Upload]
H --> I[โจ Combined Reports]
%% Styling
classDef startEnd fill:#e1f5fe,stroke:#01579b,stroke-width:2px,color:#000
classDef process fill:#f3e5f5,stroke:#4a148c,stroke-width:2px,color:#000
classDef test fill:#e8f5e8,stroke:#1b5e20,stroke-width:2px,color:#000
classDef report fill:#fff3e0,stroke:#e65100,stroke-width:2px,color:#000
classDef artifact fill:#fce4ec,stroke:#880e4f,stroke-width:2px,color:#000
class A,I startEnd
class B,C,F process
class D,E test
class G,H report
class H artifact
# Using GitHub Codespaces
# Click "Code" button on repository and select "Open with Codespaces"
# Or local development:
# Install dependencies
npm install
# Start development server
npm run dev
# Build for production
npm run build
# Run unit tests
npm run test
# Run E2E tests
npm run test:e2e
# Check license compliance
npm run test:licenses
# Generate API documentation
npm run docs:api
This template uses Three.js for high-performance 3D game rendering:
Example game component:
import { Canvas } from "@react-three/fiber";
import { OrbitControls } from "@react-three/drei";
export function Game() {
return (
<Canvas camera={{ position: [0, 2, 8], fov: 50 }}>
{/* Lighting */}
<ambientLight intensity={0.5} />
<pointLight position={[10, 10, 10]} intensity={1} />
{/* 3D Objects */}
<mesh>
<sphereGeometry args={[0.5, 32, 32]} />
<meshStandardMaterial color="#00ff88" />
</mesh>
{/* Camera Controls */}
<OrbitControls />
</Canvas>
);
}
npm run testnpm run test:e2elicense-compliancenpm run test:licensesflowchart LR
subgraph "๐ง CI Pipeline"
A1[๐ Code Changes] --> A2[๐ Lint & Type Check]
A2 --> A3[๐๏ธ Build]
A3 --> A4[๐งช Test]
A4 --> A5[๐ Report]
end
subgraph "๐ Security Pipeline"
S1[๐ก๏ธ CodeQL Analysis]
S2[๐ฆ Dependency Review]
S3[๐ OSSF Scorecard]
S4[๏ฟฝ SBOM Quality Check]
S5[๏ฟฝ๐ Runner Hardening]
end
subgraph "๐ Test Coverage"
B1[Unit Tests<br/>80%+ Coverage]
B2[E2E Tests<br/>Critical Flows]
B3[Type Safety<br/>Strict Mode]
end
subgraph "๐ฏ Outputs"
C1[๐ Coverage Reports]
C2[๐ฌ Test Videos]
C3[๐ธ Screenshots]
C4[๐ JUnit XML]
C5[๐ก๏ธ Security Reports]
end
A4 --> B1
A4 --> B2
A4 --> B3
A1 --> S1
A1 --> S2
A1 --> S3
A1 --> S4
A1 --> S5
A5 --> C1
A5 --> C2
A5 --> C3
A5 --> C4
S1 --> C5
S2 --> C5
S3 --> C5
S4 --> C5
%% Styling
classDef pipeline fill:#e3f2fd,stroke:#1565c0,stroke-width:2px
classDef security fill:#ffebee,stroke:#c62828,stroke-width:2px
classDef testing fill:#e8f5e8,stroke:#2e7d32,stroke-width:2px
classDef output fill:#fff8e1,stroke:#f57c00,stroke-width:2px
class A1,A2,A3,A4,A5 pipeline
class S1,S2,S3,S4 security
class B1,B2,B3 testing
class C1,C2,C3,C4,C5 output
This template includes a comprehensive, security-first release workflow with automated versioning, security attestations, and deployment.
flowchart TD
A[๐ Release Trigger] --> B{๐ Release Type}
B -->|๐ท๏ธ Tag Push| C[๐ Automatic Release]
B -->|โก Manual Dispatch| D[๐ Manual Release]
C --> E[๐ฆ Prepare Phase]
D --> E
E --> F[๐๏ธ Build & Test]
F --> G[๐ Security Validation]
G --> H[๐ Generate SBOM]
H --> I[๐ Create Attestations]
I --> J[๐ Draft Release Notes]
J --> K[๐ Deploy to Pages]
K --> L[๐ข Publish Release]
subgraph "๐ Security Layers"
M[SLSA Build Provenance]
N[SBOM Attestation]
O[Artifact Signing]
P[Supply Chain Verification]
end
I --> M
I --> N
I --> O
G --> P
%% Styling
classDef trigger fill:#e1f5fe,stroke:#01579b,stroke-width:2px
classDef process fill:#f3e5f5,stroke:#4a148c,stroke-width:2px
classDef security fill:#ffebee,stroke:#c62828,stroke-width:2px
classDef deploy fill:#e8f5e8,stroke:#1b5e20,stroke-width:2px
class A,B,C,D trigger
class E,F,J,K,L process
class G,H,I,M,N,O,P security
# Create and push a tag to trigger automatic release
git tag v1.0.0
git push origin v1.0.0
v1.0.1) and pre-release statusRelease notes are automatically generated using semantic labeling:
graph LR
A[๐ PR Labels] --> B[๐ Release Drafter]
B --> C[๐ Categorized Notes]
subgraph "๐ท๏ธ Label Categories"
D[๐ New Features]
E[๐ฎ Game Development]
F[๐ Security & Compliance]
G[๐ Bug Fixes]
H[๐ฆ Dependencies]
I[๐งช Test Coverage]
end
A --> D
A --> E
A --> F
A --> G
A --> H
A --> I
C --> J[๐ข GitHub Release]
classDef labels fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef process fill:#e3f2fd,stroke:#1565c0,stroke-width:2px
classDef output fill:#e8f5e8,stroke:#2e7d32,stroke-width:2px
class D,E,F,G,H,I labels
class A,B,C process
class J output
Every release includes a comprehensive SBOM in SPDX format:
{
"SPDXID": "SPDXRef-DOCUMENT",
"name": "game-v1.0.0",
"packages": [
{
"SPDXID": "SPDXRef-Package-react",
"name": "react",
"versionInfo": "19.1.0",
"licenseConcluded": "MIT"
}
]
}
SLSA-compliant build attestations provide cryptographic proof:
{
"_type": "https://in-toto.io/Statement/v0.1",
"predicateType": "https://slsa.dev/provenance/v0.2",
"subject": [
{
"name": "game-v1.0.0.zip",
"digest": {
"sha256": "abc123..."
}
}
],
"predicate": {
"builder": {
"id": "https://github.com/actions/runner"
},
"buildType": "https://github.com/actions/workflow@v1"
}
}
# Verify build provenance
gh attestation verify game-v1.0.0.zip \
--owner Hack23 --repo game
# Verify SBOM attestation
gh attestation verify game-v1.0.0.zip \
--owner Hack23 --repo game \
--predicate-type https://spdx.dev/Document
This repository uses GitHub's immutable releases to prevent unauthorized modifications to published releases.
Immutable releases lock release artifacts after publication, ensuring:
Only release title and notes can be modified after publication.
# Verify release artifacts haven't been tampered with
gh attestation verify game-v1.1.4.zip --owner Hack23 --repo game
Part of our security-first approach alongside OSSF Scorecard, SLSA attestations, and automated scanning.
Each release includes multiple artifacts with full traceability:
๐ฆ Release v1.0.0
โโโ ๐ฎ game-v1.0.0.zip # Built application
โโโ ๐ game-v1.0.0.spdx.json # Software Bill of Materials
โโโ ๐ game-v1.0.0.zip.intoto.jsonl # Build provenance attestation
โโโ ๐ game-v1.0.0.spdx.json.intoto.jsonl # SBOM attestation
sequenceDiagram
participant Dev as ๐จโ๐ป Developer
participant GH as ๐ GitHub
participant CI as ๐ CI/CD
participant Sec as ๐ Security
participant Pages as ๐ GitHub Pages
Dev->>GH: ๐ท๏ธ Push Tag/Manual Trigger
GH->>CI: ๐ Start Release Workflow
CI->>CI: ๐งช Run Tests & Build
CI->>Sec: ๐ Security Scans
Sec-->>CI: โ
Security Validated
CI->>Sec: ๐ Generate SBOM
CI->>Sec: ๐ Create Attestations
Sec-->>CI: ๐ Security Artifacts Ready
CI->>GH: ๐ Draft Release Notes
CI->>GH: ๐ฆ Upload Artifacts
CI->>Pages: ๐ Deploy Application
Pages-->>CI: โ
Deployment Success
CI->>GH: ๐ข Publish Release
GH-->>Dev: ๐ Release Complete
Track release quality and security with built-in metrics:
This template provides a secure foundation for game development:
src/components/All security workflows will automatically protect your game from common vulnerabilities and supply chain attacks, while providing full transparency through SBOM and attestations.
Happy gaming! ๐ฎ๐
Hack23/game is a public repo on GitHub by Hack23. A clean, minimal template for building games with React, TypeScript, Three.js, and Vite - built with security-first principles.
It declares no license on GitHub. Public does not mean open source: without a license, nobody is granted the right to reuse it.
Its maker has not tagged a system, so it is unknown here. Its README says what it needs.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
No. It is archived on GitHub: its maker no longer maintains it.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.

Tailscale for devcontainers and codespaces

Synthetic Autonomic Mind - An AI assistant for everyone.
Fast, easy and reliable testing for anything that runs in a browser.

Shannon is an AI pentester for web applications and APIs. It analyzes your source code, identifies attack vectors, and executes real exploits to prove vulnerabilities before they reach production.
Flutter makes it easy and fast to build beautiful apps for mobile and beyond
f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source โ self-host for your organization with complete privacy.

Citizen Intelligence Agency. Open-source intelligence platform analyzing Swedish political activities using AI and data visualization. Tracks politicians, government institutions, and parliamentary data, offering detailed insights, performance metrics, and advanced analytics.
Hack23 Public Information Security Management System:Security Through Transparency and Open Documentation Demonstrating Security Excellence Through Public ISMS Disclosure
European Parliament MCP Server - Political intelligence for AI agents
Sonarqube cloudformation plugin, IaC security supports cfn-nag/checkov
The CIA Compliance Manager is an application that helps organizations assess and manage the availability, integrity, and confidentiality of their systems and data based on customizable security levels, providing real-time cost estimates, business impact assessments, and technical implementation details.
European Parliament Political Intelligence Platform - Radical transparency - Democratic accountability - AI-generated news in 14 languages
This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/Hack23/gameTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.