@probelabs/visor 0.1.90 → 0.1.93

package/README.md

@@ -88,12 +88,26 @@ Tip: Pin releases for stability, e.g. `uses: probelabs/visor@v1`.
 Short cheatsheet for common tasks:
 
 ```bash
+# Validate configuration before running checks
+visor validate                    # Search for .visor.yaml in current directory
+visor validate --config .visor.yaml  # Validate specific config file
+
 # Run all checks with a table output
 visor --check all --output table
 
 # Filter by tags (e.g., fast/local) and increase parallelism
 visor --tags fast,local --max-parallelism 5
 
+# Analyze full PR diff vs base branch (like GitHub Actions does)
+# Auto-enabled for code-review schemas, or force with --analyze-branch-diff
+visor --analyze-branch-diff       # Analyzes diff vs main/master branch
+visor --check security --analyze-branch-diff  # Specific checks on branch diff
+
+# Simulate GitHub events for event-based check filtering
+visor --event pr_updated          # Run checks triggered by PR updates (auto for code-review)
+visor --event issue_opened        # Run checks triggered by new issues
+visor --event all                 # Run all checks regardless of event filters (default)
+
 # Emit machine‑readable results and save to a file
 visor --check security --output json --output-file visor-results.json
 
@@ -116,7 +130,7 @@ Additional guides:
 - Schema – JSON shape checks return (e.g., `code-review`).
 - Template – renders results (tables/markdown).
 - Group – which comment a check is posted into.
-- Provider – how a check runs (`ai`, `http`, `command`, `claude-code`).
+- Provider – how a check runs (`ai`, `http`, `http_client`, `command`, `log`, `github`, `claude-code`).
 - Dependencies – `depends_on` controls order; independents run in parallel.
 - Tags – label checks (`fast`, `local`, `comprehensive`) and filter with `--tags`.
 - Events – PRs, issues, `/review` comments, webhooks, or cron schedules.
@@ -153,6 +167,7 @@ Visor is a general SDLC automation framework:
  - [Step Dependencies & Intelligent Execution](#-step-dependencies--intelligent-execution)
  - [Failure Routing (Auto-fix Loops)](#-failure-routing-auto-fix-loops)
  - [Claude Code Provider](#-claude-code-provider)
+ - [GitHub Provider](#-github-provider)
  - [AI Session Reuse](#-ai-session-reuse)
  - [Schema-Template System](#-schema-template-system)
  - [Enhanced Prompts](#-enhanced-prompts)
@@ -174,9 +189,10 @@ Visor is a general SDLC automation framework:
 - Structured outputs: JSON Schema validation drives deterministic rendering, annotations, and SARIF.
 - Orchestrated pipelines: Dependencies, parallelism, and tag‑based profiles; run in Actions or any CI.
 - Multi‑provider AI: Google Gemini, Anthropic Claude, OpenAI, AWS Bedrock — plus MCP tools and Claude Code SDK.
+- Author permissions: Built-in functions to customize workflows based on contributor trust level (owner, member, collaborator, etc).
 - Assistants & commands: `/review` to rerun checks, `/visor …` for Q&A, predictable comment groups.
 - HTTP & schedules: Receive webhooks, call external APIs, and run cron‑scheduled audits and reports.
-- Extensible providers: `ai`, `http`, `http_client`, `log`, `command`, `claude-code` — or add your own.
+- Extensible providers: `ai`, `http`, `http_client`, `log`, `command`, `github`, `claude-code` — or add your own.
 - Security by default: GitHub App support, scoped tokens, remote‑extends allowlist, opt‑in network usage.
 - Observability & control: JSON/SARIF outputs, fail‑fast and timeouts, parallelism and cost control.
 
@@ -232,6 +248,37 @@ Examples:
 
 Learn more: [docs/commands.md](docs/commands.md)
 
+## 🔐 Author Permissions
+
+Customize workflows based on PR author's permission level using built-in functions in JavaScript expressions:
+
+```yaml
+checks:
+  # Run security scan only for external contributors
+  security-scan:
+    type: command
+    exec: npm run security:full
+    if: "!hasMinPermission('MEMBER')"
+
+  # Auto-approve PRs from collaborators
+  auto-approve:
+    type: command
+    exec: gh pr review --approve
+    if: "hasMinPermission('COLLABORATOR') && totalIssues === 0"
+
+  # Block sensitive file changes from non-members
+  protect-secrets:
+    type: command
+    exec: echo "Checking permissions..."
+    fail_if: "!isMember() && files.some(f => f.filename.startsWith('secrets/'))"
+```
+
+**Available functions:**
+- `hasMinPermission(level)` - Check if author has >= permission level
+- `isOwner()`, `isMember()`, `isCollaborator()`, `isContributor()`, `isFirstTimer()` - Boolean checks
+
+Learn more: [docs/author-permissions.md](docs/author-permissions.md)
+
 ## 🔇 Suppressing Warnings
 
 Suppress a specific issue by adding a nearby `visor-disable` comment.
@@ -624,3 +671,22 @@ MIT License — see [LICENSE](LICENSE)
 <div align="center">
   Made with ❤️ by <a href="https://probelabs.com">Probe Labs</a>
 </div>
+## 🧰 GitHub Provider
+
+Use the native GitHub provider for safe labels and comments without invoking the `gh` CLI.
+
+Example — apply overview‑derived labels to a PR:
+
+```yaml
+checks:
+  apply-overview-labels:
+    type: github
+    op: labels.add
+    values:
+      - "{{ outputs.overview.tags.label | default: '' | safe_label }}"
+      - "{{ outputs.overview.tags['review-effort'] | default: '' | prepend: 'review/effort:' | safe_label }}"
+    value_js: |
+      return values.filter(v => typeof v === 'string' && v.trim().length > 0);
+```
+
+See docs: docs/github-ops.md

package/action.yml

@@ -100,7 +100,7 @@ inputs:
   tags:
     description: 'Include checks with these tags (comma-separated)'
     required: false
-    default: ''
+    default: 'github'
 
   exclude-tags:
     description: 'Exclude checks with these tags (comma-separated)'

package/defaults/.visor.yaml

@@ -7,16 +7,8 @@ version: "1.0"
 # Global AI provider settings - users should configure their preferred provider
 # For CI testing, use --provider mock CLI flag instead
 
-# Run checks sequentially to ensure session reuse works correctly
-max_parallelism: 1
-
-# 🔄 AI Session Reuse Feature:
-# This configuration demonstrates the new 'reuse_ai_session' feature that allows
-# dependent checks to continue conversations with the same AI session, providing
-# context continuity and more intelligent follow-up analysis.
-#
-# Example: security-remediation reuses the session from the security check,
-# allowing the AI to reference the previous security analysis discussion.
+# Run up to 4 checks in parallel for faster execution
+max_parallelism: 4
 
 # Global fail condition - fail if critical or error severity issues are found
 fail_if: "output.issues && output.issues.some(i => i.severity === 'critical' || i.severity === 'error')"
@@ -69,36 +61,34 @@ checks:
   overview:
     type: ai
     group: overview
+    schema: overview
     prompt: |
-        # 📋 Pull Request Overview: {{ pr.title }}
-
-        {% if pr.body %}
-        ## Description
-        {{ pr.body }}
-        {% endif %}
+        You are generating PR overview, to help owners of the repository to understand what this PR is above, and help reviewer to point to the right parts of the code. First you should provide detailed but concise description, mentioning all the changes.
 
         ## Files Changed Analysis
+        After you need to summarize insights from `<files_summary>`: changed files, additions/deletions, notable patterns.
 
-        Analyze the files listed in the `<files_summary>` section, which provides a structured overview of all changes including filenames, status, additions, and deletions.
+        Next ensure you cover all below:
 
         ## Architecture & Impact Assessment
-
-        Please generate a comprehensive overview and analysis of this pull request.
-
-        Follow these instructions to create a thorough assessment:
-
-        1. **Change Impact Analysis**
-           - What this PR accomplishes
-           - Key technical changes introduced
-           - Affected system components
-
-        2. **Architecture Visualization**
-           - Create appropriate mermaid diagram(s) to visualize the changes
-           - Choose the best diagram type for the context
-           - Use multiple diagrams if needed to explain different aspects
-           - Focus on modified components and their relationships
-
-        Provide a balanced technical assessment suitable for both developers and stakeholders.
+          - What this PR accomplishes
+          - Key technical changes introduced
+          - Affected system components
+          - Include one or more mermaid diagrams when useful to visualize component relationships or flow.
+          
+        ## Scope Discovery & Context Expansion
+        - From the `<files_summary>` and code diffs, infer the broader scope of impact across modules, services, and boundaries.
+        - If your environment supports code search/extract tools, use them to peek at immediately-related files (tests, configs, entrypoints) for better context. If tools are not available, infer and list what you would search next.
+
+        You may also be asked to assign labels to PR; if so use this:
+        - `tags.review-effort`: integer 1–5 estimating review effort (1=trivial, 5=very high).
+        - `tags.label`: one of [bug, chore, documentation, enhancement, feature]. Choose the best fit.
+
+        Important:
+        - Propose `tags.review-effort` and `tags.label` only for the initial PR open event.
+        - Do not change or re-suggest labels on PR update events; the repository applies labels only on `pr_opened`.
+
+        Be concise, specific, and actionable. Avoid praise or celebration.
     on: [pr_opened, pr_updated]
 
   # Security analysis - Critical for all projects
@@ -146,7 +136,6 @@ checks:
         - **warning**: Security concerns that should be addressed (verbose errors, missing rate limiting, insecure defaults)
         - **info**: Security best practices and hardening suggestions (defense in depth, additional validation)
     depends_on: [overview]
-    reuse_ai_session: overview  # 🔄 Reuses the overview check's AI session for context continuity
     on: [pr_opened, pr_updated]
 
   # Performance analysis - Important for all applications
@@ -155,7 +144,7 @@ checks:
     group: review
     schema: code-review
     prompt: |
-        Building on our overview and security analysis, now review the code changes for performance issues.
+        Building on our overview analysis, now review the code changes for performance issues.
 
         Focus on the files listed in `<files_summary>` and analyze the code changes shown in the `<full_diff>` or `<commit_diff>` sections.
 
@@ -183,7 +172,7 @@ checks:
         - Race conditions and deadlocks
         - Inefficient parallel processing
 
-        Building on our overview and security analysis, identify performance issues and provide optimization recommendations that complement our previous findings.
+        Building on our overview analysis, identify performance issues and provide optimization recommendations.
 
         ## Severity Guidelines
         Use the following severity levels appropriately:
@@ -191,8 +180,7 @@ checks:
         - **error**: Significant performance problems affecting user experience (O(n²) in critical path, N+1 queries, blocking I/O)
         - **warning**: Performance concerns that should be optimized (inefficient algorithms, missing indexes, unnecessary operations)
         - **info**: Performance best practices and optimization opportunities (caching suggestions, async improvements)
-    depends_on: [security]
-    reuse_ai_session: overview  # 🔄 Reuses the overview check's AI session for context continuity
+    depends_on: [overview]
     on: [pr_opened, pr_updated]
 
   # Code quality and maintainability
@@ -201,7 +189,7 @@ checks:
     group: review
     schema: code-review
     prompt: |
-        Building on our overview, security, and performance discussions, evaluate the code quality and maintainability.
+        Building on our overview discussion, evaluate the code quality and maintainability.
 
         Review the code changes shown in the `<full_diff>` or `<commit_diff>` sections, considering the files listed in `<files_summary>`.
 
@@ -235,7 +223,7 @@ checks:
         - Framework/library best practices
         - Type safety (if applicable)
 
-        Focus on actionable improvements that enhance code maintainability while considering the overview, security, and performance findings we've already discussed.
+        Focus on actionable improvements that enhance code maintainability based on the overview analysis.
 
         ## Severity Guidelines
         Use the following severity levels appropriately:
@@ -243,8 +231,7 @@ checks:
         - **error**: Quality problems that significantly impact maintainability (no error handling, high complexity, severe coupling)
         - **warning**: Quality concerns that should be addressed (missing tests, code duplication, poor naming)
         - **info**: Best practices and improvement suggestions (refactoring opportunities, documentation improvements)
-    depends_on: [performance]
-    reuse_ai_session: overview  # 🔄 Reuses the overview check's AI session for context continuity
+    depends_on: [overview]
     on: [pr_opened, pr_updated]
 
   # Code style and formatting analysis
@@ -253,7 +240,7 @@ checks:
     group: review
     schema: code-review
     prompt: |
-        Building on our overview, security, performance, and quality discussions, analyze the code style and formatting consistency.
+        Building on our overview discussion, analyze the code style and formatting consistency.
 
         Review the code changes shown in the `<full_diff>` or `<commit_diff>` sections, considering the files listed in `<files_summary>`.
 
@@ -276,7 +263,7 @@ checks:
         - Documentation standards adherence
         - Code comment quality and completeness
 
-        Focus on style improvements that enhance code readability and maintainability while considering our previous analysis.
+        Focus on style improvements that enhance code readability and maintainability based on the overview analysis.
 
         ## Severity Guidelines
         Use the following severity levels appropriately:
@@ -284,135 +271,113 @@ checks:
         - **error**: Major style violations that significantly harm readability (completely inconsistent formatting, misleading names)
         - **warning**: Style inconsistencies that should be fixed (mixed conventions, unclear naming, formatting issues)
         - **info**: Style suggestions and minor improvements (spacing, comment formatting, optional conventions)
-    depends_on: [quality]
-    reuse_ai_session: overview  # 🔄 Reuses the overview check's AI session for context continuity
+    depends_on: [overview]
     on: [pr_opened, pr_updated]
 
-  # Command orchestrator - demonstrates noop type for triggering multiple checks
-  review-all:
-    type: noop
-    command: '/review'
-    depends_on: [overview, security, performance, quality, style]
-    on: [issue_comment]
-    if: "event.isPullRequest"  # Only trigger on PR comments, not issues
-    group: orchestrator
-
-  # Intelligent Issue Assistant - provides sophisticated issue triage and assistance
+  # Apply labels based on overview tags — runs only on PR open (GitHub environments only)
+  apply-overview-labels:
+    type: github
+    tags: [github]
+    depends_on: [overview]
+    on: [pr_opened]
+    op: labels.add
+    values:
+      - "{{ outputs.overview.tags.label | default: '' | safe_label }}"
+      - "{{ outputs.overview.tags['review-effort'] | default: '' | prepend: 'review/effort:' | safe_label }}"
+    value_js: |
+      return values.filter(v => typeof v === 'string' && v.trim().length > 0);
+
+  # Issue Assistant (issues only) — triage-quality prompt from main branch, structured output
   issue-assistant:
     type: ai
-    group: dynamic  # Special group: creates new comment each time instead of updating
+    group: dynamic  # New issue triage posts a standalone comment
+    schema: issue-assistant
+    prompt: |
+        You are an intelligent GitHub issue assistant for the {{ event.repository.fullName }} repository. Your role is to provide professional, knowledgeable assistance when a NEW issue is opened.
+
+        Return ONE JSON object (no prose outside JSON) that validates the `issue-assistant` schema with:
+        - `text`: write a clear, well-structured markdown reply that welcomes the reporter, shows understanding, and provides next steps. Use sections and bullets where helpful.
+        - `intent`: must be "issue_triage" for this flow.
+        - `labels` (optional): array of labels that would help organization for this new issue.
+
+        Use this triage rubric (adopted from our main prompt):
+        1) Categorize the issue - choose from: bug, chore, documentation, enhancement, feature, question, wontfix, invalid, duplicate
+        2) Assess priority (low/medium/high/urgent)
+        3) Estimate complexity (trivial/simple/moderate/complex)
+        4) Recommend labels from the categories above
+        5) Identify potential areas affected or relevant documentation
+        6) Provide an initial response with clarifying questions if needed
+
+        Response style:
+        - Professional and welcoming
+        - Actionable guidance and clear next steps
+        - Ask clarifying questions when information is missing
+        - Use markdown formatting; include code snippets where useful
+        - NEVER make promises about timelines, release dates, or team commitments
+        - NEVER say things like "we'll pick this up", "will be included in upcoming release", or "we will post updates"
+        - Focus on technical analysis and helpful information rather than commitments
+    on: [issue_opened]
+
+  # Comment Assistant (comments only) — intent detection and reply
+  comment-assistant:
+    type: ai
+    group: dynamic
+    schema: issue-assistant
     command: "visor"
-    if: "event.name === 'issues' && event.action === 'opened' || (event.name === 'issue_comment' && event.comment && event.comment.body && event.comment.body.trim().startsWith('/visor'))"
     prompt: |
-        You are an intelligent GitHub issue assistant for the {{ event.repository.fullName }} repository. Your role is to provide professional, knowledgeable assistance based on the trigger event.
-
-        ## Event Context
-        **Event Type**: {{ event.name }} - {{ event.action }}
-        {% if event.issue -%}
-        **Issue #{{ event.issue.number }}**: {{ event.issue.title }}
-        **Author**: {{ event.issue.author }}
-        **State**: {{ event.issue.state }}
-        **Created**: {{ event.issue.createdAt }}
-        {%- if event.issue.labels.size > 0 %}
-        **Labels**: {% for label in event.issue.labels %}{{ label.name }}{% unless forloop.last %}, {% endunless %}{% endfor %}
-        {%- endif %}
-        {%- if event.issue.assignees.size > 0 %}
-        **Assignees**: {% for assignee in event.issue.assignees %}{{ assignee }}{% unless forloop.last %}, {% endunless %}{% endfor %}
-        {%- endif %}
-        {%- endif %}
-        {%- if event.comment %}
-        **Comment by**: {{ event.comment.author }}
-        {%- endif %}
-
-        ## Repository Analysis Context
-        {%- if event.isPullRequest and pr.title %}
-        **PR Context**: {{ pr.title }}
-        {%- endif %}
-        {%- if event.repository %}
-        **Repository**: {{ event.repository.fullName }}
-        {%- endif %}
-
-        ## Instructions
-
-        {%- if event.name == 'issues' and event.action == 'opened' %}
-
-        **ISSUE TRIAGE MODE**
-
-        Analyze this new issue and provide intelligent triage:
-
-        ### Issue Content
-        {{ event.issue.body }}
-
-        ### Analysis Tasks
-        1. **Categorize** the issue (bug/feature/documentation/question/enhancement/maintenance)
-        2. **Assess priority** (low/medium/high/urgent) based on:
-           - Impact on users/system
-           - Security implications
-           - Blocking nature
-           - Community interest
-        3. **Estimate complexity** (trivial/simple/moderate/complex)
-        4. **Suggest timeline** for resolution
-        5. **Recommend labels** that would help with organization
-        6. **Identify stakeholders** who should be involved or assignees
-        7. **Provide initial response** to the issue author
-
-        ### Response Requirements
-        - Be professional and welcoming
-        - Show you understand the request
-        - Provide clear next steps
-        - Ask clarifying questions if needed
-        - Include technical insights where appropriate
-
-        {%- elsif event.name == 'issue_comment' %}
-
-        **ASSISTANCE MODE**
-
-        A user has asked a question or provided additional information. Provide helpful technical assistance:
-
-        ### Original Issue
-        {%- if event.issue.title %}
-        **Title**: {{ event.issue.title }}
-        {%- endif %}
-        {%- if event.issue.body %}
-        **Description**: {{ event.issue.body }}
-        {%- endif %}
-
-        ### Latest Comment
-        {{ event.comment.body }}
-
-        ### Analysis Tasks
-        1. **Understand the context** of their question/comment
-        2. **Provide technical guidance** based on project knowledge
-        3. **Reference relevant code/files** if applicable
-        4. **Suggest implementation approaches** for feature requests
-        5. **Provide debugging steps** for bug reports
-        6. **Link to documentation** or similar issues if helpful
-        7. **Offer code examples** when appropriate
-
-        ### Response Requirements
-        - Address their specific question directly
-        - Provide actionable guidance
-        - Be encouraging and supportive
-        - Use technical language appropriate to their level
-        - Include code examples where helpful
-        - Reference project conventions and patterns
-
-        {%- endif %}
-
-        ### Special Instructions
-        - Always be professional, helpful, and encouraging
-        - Focus on actionable advice and clear next steps
-        - Use markdown formatting for better readability
-        - Include relevant code examples when helpful
-        - Reference project context and patterns when applicable
-        - If dealing with `/visor` commands in comments, acknowledge and provide assistance
-        - Maintain consistency with project tone and contributor guidelines
-
-        ### Response Format
-        Provide a well-structured markdown response with clear sections and helpful guidance.
-    on: [issue_opened, issue_comment]
-
-# Output configuration
+        You are the GitHub comment assistant for {{ event.repository.fullName }}. Respond to user comments on issues or PR discussion threads.
+
+        Return ONE JSON object (no prose outside JSON) that validates the `issue-assistant` schema with:
+        - `text`: a concise, helpful markdown reply to the latest comment.
+        - `intent`: choose one: "comment_reply" (normal reply) or "comment_retrigger" (pick this ONLY when the user explicitly asks to re-run checks OR explicitly asks to disable some checks).
+        - `labels`: omit for comments (do not include).
+
+        Rules:
+        - Never suggest rerun/disable unless asked explicitly.
+        - If asked to disable any check(s), set `intent` = "comment_retrigger" and in `text` acknowledge the request and say the checks will be re-run; DO NOT propose slash/directive comments.
+        - Stay technical, direct, and specific; add code snippets or links when helpful.
+    on: [issue_comment]
+    on_success:
+      goto_js: |
+        const intent = (typeof output === 'object' && output) ? output.intent : undefined;
+        const isComment = (event && event.name) ? (event.name == 'issue_comment') : true;
+        const allowed = typeof hasMinPermission === 'function' ? hasMinPermission('MEMBER') : true;
+        return (isComment && allowed && intent === 'comment_retrigger') ? 'overview' : null
+      goto_event: pr_updated
+
+  # Apply labels to new issues based on assistant output (GitHub-only)
+  apply-issue-labels:
+    type: github
+    tags: [github]
+    depends_on: [issue-assistant]
+    on: [issue_opened]
+    op: labels.add
+    value_js: |
+      try {
+        const labels = outputs['issue-assistant']?.labels;
+        if (!Array.isArray(labels)) return [];
+        // Sanitize labels: remove non-alphanumeric chars except :/ and collapse repeated /
+        return labels
+          .map(v => v == null ? '' : String(v))
+          .map(s => s.replace(/[^A-Za-z0-9:\/]/g, '').replace(/\/{2,}/g, '/'))
+          .filter(s => s.length > 0);
+      } catch (error) {
+        log('Error processing issue labels:', error);
+        return [];
+      }
+
+  # External origin labelling for PRs and Issues
+  external-label:
+    type: github
+    tags: [github]
+    on: [pr_opened, issue_opened]
+    if: "!isMember() && !isContributor()"
+    op: labels.add
+    values:
+      - "external"
+
+  # Retrigger noop removed — comment-assistant schedules overview directly
+
 output:
   pr_comment:
     format: markdown

package/dist/13.index.js

@@ -0,0 +1,82 @@
+"use strict";
+exports.id = 13;
+exports.ids = [13];
+exports.modules = {
+
+/***/ 31223:
+/***/ ((__unused_webpack_module, exports, __webpack_require__) => {
+
+
+/*
+ * Copyright The OpenTelemetry Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+Object.defineProperty(exports, "__esModule", ({ value: true }));
+exports.execAsync = void 0;
+const child_process = __webpack_require__(35317);
+const util = __webpack_require__(39023);
+exports.execAsync = util.promisify(child_process.exec);
+//# sourceMappingURL=execAsync.js.map
+
+/***/ }),
+
+/***/ 80013:
+/***/ ((__unused_webpack_module, exports, __webpack_require__) => {
+
+
+/*
+ * Copyright The OpenTelemetry Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+Object.defineProperty(exports, "__esModule", ({ value: true }));
+exports.getMachineId = void 0;
+const process = __webpack_require__(932);
+const execAsync_1 = __webpack_require__(31223);
+const api_1 = __webpack_require__(63914);
+async function getMachineId() {
+    const args = 'QUERY HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Cryptography /v MachineGuid';
+    let command = '%windir%\\System32\\REG.exe';
+    if (process.arch === 'ia32' && 'PROCESSOR_ARCHITEW6432' in process.env) {
+        command = '%windir%\\sysnative\\cmd.exe /c ' + command;
+    }
+    try {
+        const result = await (0, execAsync_1.execAsync)(`${command} ${args}`);
+        const parts = result.stdout.split('REG_SZ');
+        if (parts.length === 2) {
+            return parts[1].trim();
+        }
+    }
+    catch (e) {
+        api_1.diag.debug(`error reading machine id: ${e}`);
+    }
+    return undefined;
+}
+exports.getMachineId = getMachineId;
+//# sourceMappingURL=getMachineId-win.js.map
+
+/***/ })
+
+};
+;

package/dist/159.index.js

@@ -0,0 +1,38 @@
+"use strict";
+exports.id = 159;
+exports.ids = [159];
+exports.modules = {
+
+/***/ 31159:
+/***/ ((__unused_webpack_module, exports, __webpack_require__) => {
+
+
+/*
+ * Copyright The OpenTelemetry Authors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *      https://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+Object.defineProperty(exports, "__esModule", ({ value: true }));
+exports.getMachineId = void 0;
+const api_1 = __webpack_require__(63914);
+async function getMachineId() {
+    api_1.diag.debug('could not read machine-id: unsupported platform');
+    return undefined;
+}
+exports.getMachineId = getMachineId;
+//# sourceMappingURL=getMachineId-unsupported.js.map
+
+/***/ })
+
+};
+;