Claude Code

Terminal coding agent that reads and edits a local project while routing requests to Anthropic services.

Score calculation

(6 + 2 + 4 + 3) ÷ 4 = 3.8

4 of six dimensions rated. Unrated dimensions and BDS status are excluded.

Setup details

The public repository contains the product wrapper/docs and plugins, but its license reserves rights; model and hosted service are separate.

Energy

↑

Claude Code does not publish service-specific energy or water data; the model and serving provider determine most inference impact.

Reasoning & sources

Claude Code requires a network connection for inference and supports Anthropic’s API plus Bedrock and Vertex deployments. That gives buyers a provider choice, but the docs provide no workload-level electricity, water, or emissions data. Choose a provider with regional energy reporting and compare the same model and task before treating one route as lower impact.

No per-task electricity, water, or emissions data, serving-region breakdown, or lifecycle assessment was found for the harness.

Claude Code provider and network requirements ↗

Training rights

↑

Claude Code is a harness that connects to models; its sources do not establish a complete rights record for the training data of every model it can use.

Reasoning & sources

Claude Code itself does not disclose a training corpus for its model; the model is Anthropic-hosted by default, with enterprise routes through Bedrock or Vertex. Anthropic’s consumer and commercial policies give different training rules, but neither page provides a source-level rights ledger. Check the exact account and provider terms, or use a separate local-model harness if you need to inspect the corpus before sending code.

The provider and exact model vary by configuration; no complete rights ledger can be inferred from the harness license or provider list.

Privacy

↑

Anthropic’s Claude Code data rules vary by consumer versus commercial account and opt-in/safety-review state.

Reasoning & sources

Use Claude Code only after checking the account path: consumer, commercial, API, and ZDR terms differ, so a general “Claude privacy” claim does not fit every session. Turn off training where available and confirm where logs are retained for the exact provider route.

Plan, selected model/provider, enabled features, and deployment mode can change this assessment.

Openness

↑

The product repository is public, but its license reserves rights; it is not open-source software.

Reasoning & sources

Claude Code’s public repository makes client code and plugins inspectable, but its license reserves rights and does not make the software open source. This access does not expose Claude models or Anthropic’s hosted inference service. Treat the editor and model as separate parts of the stack.

This score covers the harness/editor source only; hosted services, models, data, or enterprise features may remain proprietary.

Worker treatment

↑

Anthropic’s 2025 Claude 4 system card and inbound-services agreement disclose use of paid data-labeling contractors and require crowd-work vendors to follow minimum worker-wellbeing expectations. Stanford FMTI found no public worker compensation, location, or top-source labor-practice outcomes, so the standards remain policy commitments rather than independently verified results.

Reasoning & sources

Public vendor-wellbeing standards and contractor disclosure are meaningful, but Stanford FMTI found no compensation or worker-level outcomes for the principal data sources. This is relevant when deciding whose business to support, while pay and working conditions for the team behind Claude Code remain unestablished. Ask for current worker outcomes for that team and its suppliers.

Stanford’s 2025 assessment says Anthropic uses paid contractors and data-work platforms, but finds its public disclosure incomplete on worker pay, locations, and protections. This concerns model-development labor rather than Claude Code’s software team. Ask Anthropic for current vendor-level worker standards and independent verification before relying on its model services.

Public vendor-wellbeing standards and contractor disclosure are meaningful, but Stanford FMTI found no compensation or worker-level outcomes for the principal data sources. This rating describes the company relationship or supplier policy, not a finding about this particular product’s use.

Working conditions for the people building or supporting Claude Code are not established by this company-wide record. Current pay, vendor locations, worker exposure, and compliance/audit results are not published per major data source.

Government & military

↑

Anthropic reports a two-year DoD CDAO prototype agreement with a $200 million ceiling, Claude in classified Palantir mission workflows, and Claude Gov deployments on AWS for national-security agencies. In March 2026, Anthropic said DoW designated it a supply-chain risk, narrowly applying to Claude use directly under DoW contracts, and that it would support a transition for warfighters.

Reasoning & sources

The company documents classified defense use and a $200 million prototype agreement; deployments and guardrails are not independently assessed. This is relevant when deciding whose business to support. Deployment of Claude Code or this particular model release under those contracts remains unestablished; consider the company relationship separately from the product’s actual use.

Anthropic announced a two-year DoD prototype with a $200 million ceiling and public responsible-use limits. This is a direct company relationship, not proof that Claude Code itself was deployed. Buyers can weigh Anthropic’s provider relationship and ask which products and models were used.

The company documents classified defense use and a $200 million prototype agreement; deployments and guardrails are not independently assessed. This rating describes the company relationship or supplier policy, not a finding about this particular product’s use.

Deployment of Claude Code under these contracts is not established. These company statements do not establish the specific operational outcomes or independently assess the safeguards of deployments.

BDS status

↑

We did not find Anthropic among the named targets in the two official BNC campaign lists. This is a limited list check, not BDS approval.

Reasoning & sources

Anthropic is not a named target in the checked lists, but BDS uses selective campaigns, so absence cannot establish a clean record. Anthropic names AWS as its primary training and cloud provider and reports a large compute commitment and Amazon investment. This connects its business to a BDS pressure target without making Anthropic a separately named target; the announcement does not identify the host of every Claude request.

This review covers the named targets in the BNC consumer/pressure guide and No Tech campaign, not every BDS campaign, local group, investment or supplier. Lists and ownership can change. A company’s absence from these lists is not an endorsement or proof that it has no relevant relationships.

All sources