---
name: Progmaweb bug
about: Report a problem with Progmasoft, accounts, or ViGet
title: "[Bug] "
---

<!-- SPDX-FileCopyrightText: 2026 Progmasoft <support@progmasoft.com> -->
<!-- SPDX-License-Identifier: AGPL-3.0-or-later WITH AdditionRef-Progmasoft-Patent-Grant-1.1 -->

This repository owns `progmasoft.com`, `account.progmasoft.com`, and `viget.progmasoft.com`. Tala language pages and compiler behavior belong in their separate repositories. Never post passwords, verification codes, OAuth secrets, session cookies, email headers containing private data, or access tokens. Send security vulnerabilities privately to support@progmasoft.com.

### Affected host and flow

- Host and sanitized path:
- Area (corporate page, account registration/login/recovery, dashboard, ViGet package catalog, DSL plugin catalog, API, localization, or theme):
- Account state needed to reproduce (signed out, newly registered, signed in), without identifying a real account:

### Observed and expected behavior

Describe what happened, what you expected, and any visible status code or safe error message. If the issue involves a package path, distinguish `/langs/tala/<Publisher>/<Name>/` ViPkgs from `/dslplugins/tazel/<Publisher>/<Name>/` JAR plugins; do not attach private packages.

### Reproduction

List the shortest safe steps. For account or authorization issues, use redacted request/response details and say whether the problem also occurs in a fresh private browser session. Do not publish a real email address unless you intentionally want it public.

### Environment

- Browser and version, OS, and viewport:
- Locale (`en-US` or `de-DE`) and light/dark theme:
- Approximate incident time and time zone:
- Progmaweb commit or deployment version, if known:

### Evidence

Attach a sanitized screenshot, browser-console message, or request ID. State whether the problem affects one host or multiple Progmasoft hosts.