Landscape
26.08 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on Landscape's page any more, so we've brought you to the top.
Landscape is a systems management tool that automates security patching, auditing, access management, and compliance tasks across Ubuntu estates.
landscape-config --show landscape-client --script-tempdir /var/lib/landscape/tmp landscape-config --authenticated-attach-code <your-attach-code> landscape-config --silent --account-name <account> --url <server-url> snap set landscape <key>=<value>
What you can do now
Summary
Landscape is an open-source endpoint-management server that manages Ubuntu machines through an installed client agent, with licensing and support available through Ubuntu Pro. System administrators and compliance teams run it on-premises or in the cloud, using its web portal or API to manage fleets ranging from desktops and servers to IoTIoTA collective label for internet-connected physical devices — sensors, cameras, routers, appliances — that tools target because they run embedded firmware with limited patching and broad network exposure. devices. Its documentation positions it as a central system for Ubuntu administration, including repository profiles, Ubuntu Core and snap management, USG hardening profiles, and non-interactive registration for provisioning pipelines. Launched in 2008, it has had eight tracked releases and released this week.
Landscape is a systems management tool that automates security patching, auditing, access management, and compliance tasks across Ubuntu estates.
How Landscape helps
Which Ubuntu machines are in my estate, and what are their current details?
The client reports each managed machine’s inventory, including hardware, network interfaces, cloud-init data, snapd information, and device identity, while excluded package sources or unreported data remain outside the inventory.
Which machines are missing required security updates?
Landscape collects package information from enrolled clients, applies available updates and security patches centrally, and reports the resulting fleet status; it only covers machines that are registered and communicating with the server.
What software, repositories, and snaps are deployed across my Ubuntu fleet?
The server inventories installed software and source channels, then lets administrators deploy packages, manage repository profiles, and manage snaps and snap services across selected machines; the view reflects the client’s latest report rather than an unreported local change.
Which systems fail our Ubuntu security or compliance requirements?
Landscape runs auditing and compliance checks across enrolled Ubuntu systems, supports Ubuntu Security Guide hardening profiles, and generates reports identifying machines that do not meet the selected requirements.
How do I register newly provisioned machines without stopping a provisioning pipeline for approval?
The client can send a registration message non-interactively, use an authenticated attachment code to associate the machine with the right account, and report an installation request identifier; this only establishes enrollment and does not by itself perform later management actions.
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for Landscape, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Landscape puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
ubuntu.com, every changeCanonical's 38 pages as they looked each month from October 2026 to November 2026: 40 renders, 2 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Brand changes
Each row is a name, owner or logo change we've confirmed. The dates are the last capture before it and the first one after. A new page design on its own isn't counted. Spot one that's wrong? Use “Not a rebrand” on its row.
We spotted these but haven't confirmed them yet, so they aren't counted above.
Documentation timing
See whether Landscape's docs change before or after its release notes, release by release.
Documentation timing is included with Practitioner, Researcher and Business. When the docs come first, you can read about a change before it's announced.
See plans → Already subscribed? Sign in →We check each docs page on a fixed schedule, so every gap is a range rather than one number. A release we can't place on either side is shown as "Can't tell".
Releases
10 entries
No entries match these filters.
- November 20261
- August 20261
- February 20261
- October 20251
- August 20251
- May 20251
- November 20241
- August 20241
- April 20241
- February 20241
Articles
6 articles · updated Nov 10, 2026Where Landscape turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
-
The npm Threat Landscape: Attack Surface and Mitigations (Updated July 15)
…worm, a self-replicating malware that automated the compromise and redistribution of malicious packages, marked the end of the “nuisance” era of npm attacks and the beginning of a high-consequence threat landscape.
-
Netscaler Exploitation to Social Engineering | Huntress
…overlaps with various trends currently observed in the information landscape: living off the land binaries ( LOLBins ) and behaviors, emphasis on evasion and obfuscation, and even the use of non-standard means to…
-
Investigating New INC Ransom Group Activity | Huntress
The Huntress team is always keeping our eye on the evolving threat landscape.
-
One MSP, Three Microsoft 365 Compromises, 72 Hours | Huntress
Read Part Two: Threat Hunting for Business Email Compromise Through User Agents Setting the Stage The cybersecurity landscape is evolving and creating new challenges for Managed Service Providers (MSPs).
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.