Skip to content

javascript repo updates#3255

Open
angela-zhang wants to merge 2 commits intomainfrom
repository-edits
Open

javascript repo updates#3255
angela-zhang wants to merge 2 commits intomainfrom
repository-edits

Conversation

@angela-zhang
Copy link
Copy Markdown
Contributor

@angela-zhang angela-zhang commented Apr 20, 2026

  • Update guidance on artifact manager setup to use Chainguard Repo
  • Add cooldown configuration docs

@angela-zhang angela-zhang requested a review from a team as a code owner April 20, 2026 13:43
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 20, 2026

Deploy Preview for ornate-narwhal-088216 ready!

Name Link
🔨 Latest commit 8387ef9
🔍 Latest deploy log https://app.netlify.com/projects/ornate-narwhal-088216/deploys/69e630d659728c0008ad18e4
😎 Deploy Preview https://deploy-preview-3255--ornate-narwhal-088216.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@angela-zhang angela-zhang requested review from ajayk and s-stumbo April 20, 2026 13:44
Signed-off-by: angela-zhang <30538317+angela-zhang@users.noreply.github.com>
Repository provides.

However, if upstream fallback is not enabled or you prefer to manage your own fallback
ordering: you can configure `https://libraries.cgr.dev/javascript/` as a remote
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ordering, you can

* **After the cooldown period**: The package is checked against malware scanning. If it passes, it is proxied from the npm Registry.
* **Malware detected**: Any package version with a known malware identifier (MAL ID) is blocked and never served, whether it originates from Chainguard builds or the npm upstream. Malware scanning runs on all packages, including those proxied from npm.
* Malware scanning checks all packages against the Open Source Vulnerabilities (OSV) database, which includes the OpenSSF Malicious Packages feed among other sources. Any package version flagged with a malware identifier is blocked before it can be served. This covers reported malicious packages across the npm ecosystem; packages with unreported or novel malware may not be detected by scanning alone, which is why building from verified source remains the primary defense. No newline at end of file
* Malware scanning checks all packages against the [Open Source Vulnerabilities (OSV) database](https://osv.dev/), which includes the OpenSSF Malicious Packages feed among other sources. Any package version flagged with a known MAL ID is blocked before it can be served. This covers reported malicious packages across the npm ecosystem; packages with unreported or novel malware may not be detected by scanning alone, which is why building from verified source remains the primary defense.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove "before it can be served" .. that makes it sound like it might get served anyway eventually.

Also npm ecosystem. Packages .. however the logic in that last sentence does really make sense to me, and it also glosses over the fact that we dont scan code ourselves.. so the defense is just that malware source code is missing typically. But for example, what if it is loaded remotely and we dont detect the loader?

* Malware scanning checks all packages against the Open Source Vulnerabilities (OSV) database, which includes the OpenSSF Malicious Packages feed among other sources. Any package version flagged with a malware identifier is blocked before it can be served. This covers reported malicious packages across the npm ecosystem; packages with unreported or novel malware may not be detected by scanning alone, which is why building from verified source remains the primary defense. No newline at end of file
* Malware scanning checks all packages against the [Open Source Vulnerabilities (OSV) database](https://osv.dev/), which includes the OpenSSF Malicious Packages feed among other sources. Any package version flagged with a known MAL ID is blocked before it can be served. This covers reported malicious packages across the npm ecosystem; packages with unreported or novel malware may not be detected by scanning alone, which is why building from verified source remains the primary defense.

> **Note**: Chainguard Repository for JavaScript is not a full mirror of npm. With fallback enabled, Chainguard does not guarantee that evey package and version on npm will be available. Packages can be delayed by cooldown or permanently blocked by malware policies.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is backwards.. we should point out that is is not a full mirror on purpose and why (no malware). That invalidates the whole talk about "guarantee"

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.

3 participants