Automic VaultAutomic Vault

brew

Install dscanner with Homebrew, Nix, pacman

Analyses e.g. the style and syntax of D code. Version 0.15.2 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install dscanner

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#dscanner

nixpkgs package indexes · pkgs/by-name/ds/dscanner/package.nix · source: api.github.com

Arch Linux pacmanverified · 92%
sudo pacman -S dscanner

Arch Linux sync databases · dscanner · source: geo.mirror.pkgbuild.com

overview

Package summary

Analyses e.g. the style and syntax of D code

Commands and aliases

  • dscanner

history

Project history and usage

D-Scanner is a command-line analysis tool for D source code. It sits in the D language tooling layer as a linter, syntax/style checker, import/token helper, and machine-readable reporting tool for editors and CI.

Project history

The project is maintained under the dlang-community organization and is documented as a source-code analysis tool for D. Its README describes native builds with D compilers, DUB-based installation, Docker usage, linting, autofix support, custom error formats, and GitHub Actions output.

Adoption history

D-Scanner's adoption is largely within the D ecosystem rather than general-purpose developer tooling. Its README notes that many D editors already ship with D-Scanner integration, while package entries in Homebrew, Nix, Arch, and DUB make it available through both system and language package workflows.

How it is used

Typical usage includes `dscanner lint source/` for human-readable diagnostics, `dscanner fix source/` for interactive fixes, `--report` or custom formats for tool integration, and `dscanner.ini` to enable or disable diagnostics.

Why package nerds care

D-Scanner matters to package maintainers because language tooling often needs to be installed outside the language package manager for editor and CI integration. It is a small example of how ecosystem-specific linters become system packages when they need a stable executable on PATH.

Timeline

  • 2010s: D-Scanner becomes part of the D language community tooling ecosystem.
  • Later: The README documents DUB, Docker, editor, CI, autofix, and `dscanner.ini` workflows.
  • Community era: The project is maintained in the `dlang-community` GitHub organization.

Related projects

  • DUB is the D package manager installation path documented by the project.
  • DMD, LDC, and GDC are supported compiler/build targets called out in the README.
  • D editors and GitHub Actions are integration targets for D-Scanner output.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 12 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
dscanner.ini
Windows
dscanner.ini

executables

Installed executables

CommandKindExposureNote
dscannercliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.15.2
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/dlang-community/D-Scanner

install metadata

Package metadata

Package keybrew:dscanner
Version0.15.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/dscanner
Homepagehttps://github.com/dlang-community/D-Scanner
Repositoryhttps://github.com/dlang-community/D-Scanner
Upstream docshttps://github.com/dlang-community/D-Scanner#readme
LicenseBSL-1.0
Source archivehttps://github.com/dlang-community/D-Scanner.git
Build dependenciesldc
Bottleavailable (on arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedscanner
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

dscanner

nix profile install nixpkgs#dscanner
  • normalized package name match
  • Matched by: Dscanner
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ds/dscanner/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
pacman95%

dscanner 0.15.2-2

Swiss-army knife for D source code

https://github.com/dlang-community/D-Scanner

sudo pacman -S dscanner
  • License: BSL-1.0
  • Architecture: x86_64
  • 1 dependencies
  • normalized package name match
  • Matched by: Dscanner
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: dscanner from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment