chore(license): set SPDX license metadata to match Apache-2.0 LICENSE

[KooshaPari]

User description

Summary

Per worklogs/GOVERNANCE.md LICENSE coverage audit (task #106).

BytePort already carries a canonical Apache-2.0 LICENSE at the repo root, so no LICENSE file changes are needed here. This PR is a metadata-only fix: align Cargo.toml and package.json files to declare the SPDX license identifier so crates.io / npm / GitHub licensee detection all agree with the on-disk LICENSE.

Changes

• frontend/web/src-tauri/Cargo.toml: license = "" → "Apache-2.0"
• frontend/web/package.json: add "license": "Apache-2.0"
• .github/frontend/package.json: add "license": "Apache-2.0"

Why

• Unblocks crates.io / npm publishing (SPDX-compliant identifier)
• Declared license now matches the repo's on-disk LICENSE text

Sister PRs: PhenoKits#14, PhenoPlugins#3, PhenoMCP#5, DataKit#4, Tracera#341.

Test plan

• cargo metadata in frontend/web/src-tauri reports license: "Apache-2.0"
• npm view / package managers see the new license field

---

Note

Low Risk
Low risk metadata-only change that only affects package manifest fields for publishing/license detection.

Overview
Sets SPDX license metadata to Apache-2.0 in .github/frontend/package.json and frontend/web/package.json, and replaces the empty license field in frontend/web/src-tauri/Cargo.toml with Apache-2.0 so npm/crates tooling and GitHub license detection align with the repo LICENSE.

^{Reviewed by Cursor Bugbot for commit 8aff456. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Add Apache-2.0 license metadata to frontend packages

What Changed

• The Rust app manifest now declares Apache-2.0 as its license instead of leaving it blank
• The frontend package files now also declare Apache-2.0, so license information matches the repo’s LICENSE file
• This makes the project’s license easier for package registries and code hosting sites to recognize

Impact

✅ Clearer license display on package pages
✅ Fewer publishing issues for frontend and Rust packages
✅ Consistent license detection across registries and GitHub

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• .github/frontend/package.json — added "license": "Apache-2.0"
• frontend/web/package.json — added "license": "Apache-2.0"
• frontend/web/src-tauri/Cargo.toml — changed license = "" → "Apache-2.0"

---

_{Reviewed by step-3.5-flash · 86,751 tokens}

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[gemini-code-assist]

Code Review

This pull request adds the Apache-2.0 license to configuration files across the frontend and Tauri components. A review comment highlights a potential conflict in .github/frontend/package.json, where the private property remains set to true, which may prevent the package from being published as intended.

[gemini-code-assist]

This package is marked as "private": true (on line 4), which prevents it from being published to npm. While adding a license is good for metadata, it appears to conflict with the private setting and the PR's stated goal of unblocking publishing. If this package is intended for publication, consider removing "private": true. If it is intended to be private, this change is fine for consistency, but please be aware that it will not enable publishing.