c/side
Introducing CSP Builder commercialThe section your link pointed to isn't on c/side's page any more, so we've brought you to the top.
C/Side is a cloud-based IDE for Dynamics 365 Business Central development, enabling creation and modification of extensions and customizations.
Summary
c/side is a commercial web-app-security service that monitors client-side scripts running in the browser to catch malicious or unwanted behavior — ad injection, redirect abuse, bot and AI agent traffic, and browsers spoofed by VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. clients — before they compromise site visitors. It runs as a hosted dashboard, with a Cmd+K command palette for jumping across monitored domains and a Notifications Engine that routes alerts into Linear or Jira for remediation. It's aimed at application security and fraud teams responsible for third-party scripts and PCIPCIA hardware bus standard that connects peripheral devices to a computer's motherboard; cyber tools targeting hardware-level forensics or memory analysis use it to access device registers and DMA regions directly. compliance rather than at network-layer defenders; a guided setup flow tailors onboarding to goals like PCI, fraud prevention, or device fingerprinting. Its CSPCSPContent Security Policy: a browser security mechanism, standardized by the W3C, that lets a web server declare which sources of scripts, styles, and other resources a page may load, blocking injection attacks. Builder generates and lets teams tune a Content-Security-Policy from observed hosts, with a report-only mode before enforcement. The project shows steady development, with 10 releases in the window we track.
C/Side is a cloud-based IDE for Dynamics 365 Business Central development, enabling creation and modification of extensions and customizations.
How c/side helps
Which third-party scripts on my site are injecting ads or hijacking content?
flags client-side scripts exhibiting ad-injection behavior such as iframe data population and unexpected URL resolution, naming the script and the page it ran on
Which of my visitors are actually bots or AI agents, not real users?
separates automated traffic from human traffic using fingerprint and agent signals, so suspicious script activity can be traced to the traffic that triggered it
Is one of my visitors really a browser, or a VPN client pretending to be one?
fingerprints the full TLS handshake per connection and flags mismatches between the claimed browser and the cipher suites, extensions, and ALPN it actually presents
Which script just redirected a visitor somewhere it shouldn't?
alerts when a script produces five or more redirects in a chain, so runaway or malicious redirect behavior gets caught before it reaches visitors
What should my Content-Security-Policy actually allow, given what my site really loads?
builds a suggested policy from hosts already observed on the site, lets you toggle off unexpected ones, and can run it in report-only mode so you see what it would have blocked before enforcing it
Which alerts need to land in front of which team, and where do they go to get fixed?
routes alerts by configurable rule into Linear or Jira, turning a detection straight into a tracked issue instead of a dashboard notification someone has to notice
Languages
Screenshots
From the release notes, newest first. Click one to see it full size.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
Five scores for c/side, 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 c/side 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…
Releases
23 entries
No entries match these filters.
- August 20262
- July 20268
- May 20263
- March 20262
- January 20261
- December 20251
- July 20252
- April 20251
- February 20251
- December 20241
- July 20241
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.