Skip to content

fix: prefer NVM_ACCESS_TOKEN for malware feed license header - #34

Merged
coreybutler merged 1 commit into
mainfrom
fix/malware-feed-env-token
Nov 6, 2026
Merged

coreybutler merged 1 commit into
mainfrom
fix/malware-feed-env-token

Conversation

@coreybutler

Copy link
Copy Markdown
Contributor

What

LicenseHeader reads NVM_ACCESS_TOKEN / NVM_LICENSE before the installed AccessToken so pack/CI can seed malware.db.

Why

Community temporary tokens get HTTP 401 from the malware CDN. Release builds need an explicit token to ship a seed with the installer.

Testing

  • go test ./malwaredb -run LicenseHeader

Risk

Env token overrides registry AccessToken when set; intended for CI/pack only.

Pack/CI seed fetches need an explicit token; temporary community JWTs
are rejected by the CDN (HTTP 401). Read NVM_ACCESS_TOKEN/NVM_LICENSE
before the installed AccessToken.

Signed-off-by: Corey Butler <770982+coreybutler@users.noreply.github.com>
@coreybutler
coreybutler merged commit 60cc69b into main Nov 6, 2026
2 checks passed
@coreybutler
coreybutler deleted the fix/malware-feed-env-token branch November 6, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant