Security: microsoft/hve-core

Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include Microsoft, Azure, DotNet, AspNet and Xamarin.

If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's definition of a security vulnerability, please report it to us as described below.

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them to the Microsoft Security Response Center (MSRC) at https://msrc.microsoft.com/create-report.

If you prefer to submit without logging in, send email to secure@microsoft.com. If possible, encrypt your message with our PGP key; please download it from the Microsoft Security Response Center PGP Key page.

You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at microsoft.com/msrc.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

• Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
• Full paths of source file(s) related to the manifestation of the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our Microsoft Bug Bounty Program page for more details about our active programs.

We prefer all communications to be in English.

Microsoft follows the principle of Coordinated Vulnerability Disclosure.

For comprehensive security documentation including security models and security controls, see Security Documentation.

HVE Core publishes cryptographically attested assets under exact channel tags:

• PreRelease: prerelease-v<version>
• Stable: v<version>

1. Install the GitHub CLI if not already available:

   # Windows (winget)
   winget install GitHub.cli
   
   # macOS (Homebrew)
   brew install gh

2. Download assets from the exact channel tag you intend to verify:

   # PreRelease
   gh release download prerelease-v<version> -R microsoft/hve-core \
     -p '*.vsix' -p '*.vsix.spdx.json' -p '*.vsix.sigstore.json' \
     -p '*.vsix.intoto.jsonl' -p 'dependencies.spdx.json'
   
   # Stable
   gh release download v<version> -R microsoft/hve-core \
     -p '*.vsix' -p '*.vsix.spdx.json' -p '*.vsix.sigstore.json' \
     -p '*.vsix.intoto.jsonl' \
     -p 'hve-core.openvex.json' -p 'dependencies.spdx.json'

3. Verify each primary package with its channel and artifact signer:

   # Stable VSIX
   gh attestation verify hve-core-<version>.vsix -R microsoft/hve-core \
     --signer-workflow microsoft/hve-core/.github/workflows/extension-provenance.yml
   
   # PreRelease VSIX
   gh attestation verify hve-core-<version>.vsix -R microsoft/hve-core \
     --signer-workflow microsoft/hve-core/.github/workflows/extension-provenance.yml

The GitHub Release is the canonical verification surface for SLSA and Sigstore provenance. Marketplace publication uses the verified release VSIX, while VS Code separately verifies the Marketplace signature during installation.

A successful verification confirms:

• The artifact was built from the microsoft/hve-core repository
• The build occurred in GitHub Actions
• The artifact has not been modified since signing

Both channels publish a per-VSIX SPDX SBOM and dependencies.spdx.json. These documents are attached as SPDX predicates over the VSIX subject. Because the per-artifact and dependency predicates share the SPDX 2.3 predicate type, one verification can match more than one attestation. For commands and inspection guidance, see the SBOM Verification Guide.

The Stable release publishes hve-core.openvex.json; the current PreRelease workflow does not. The Stable vex-attest.yml workflow emits two attestations: build provenance for the OpenVEX file as a subject, and an OpenVEX predicate over dependencies.spdx.json as a subject.

gh attestation verify hve-core.openvex.json -R microsoft/hve-core \
  --signer-workflow microsoft/hve-core/.github/workflows/vex-attest.yml

gh attestation verify dependencies.spdx.json -R microsoft/hve-core \
  --signer-workflow microsoft/hve-core/.github/workflows/vex-attest.yml \
  --predicate-type https://openvex.dev/ns/v0.2.0

For download, verification, status interpretation, and how to apply it with Trivy or Grype, see the VEX Verification Guide.

Attested primary artifacts can have these companion files:

The .sigstore.json bundle contains the full Sigstore verification material. The .intoto.jsonl file is the DSSE envelope extracted from the bundle for tools that consume in-toto provenance directly.

Per-artifact SBOM files are predicate payloads, not independently attested subjects. dependencies.spdx.json is an SPDX predicate payload on both channels and is additionally a Stable subject for the OpenVEX predicate.

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.