npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007

Closed
#1008
Closed
npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
#1008

Description

@minorun365
minorun365
opened on Apr 29, 2026

Description

Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.

Steps to Reproduce

  1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
  2. Observe the warning in the output

Expected Behavior

npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).

Actual Behavior

npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

CLI Version

  • 0.12.0 (latest)
  • 1.0.0-preview.3 (preview)

Both are affected.

Operating System

macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)

Additional Context

Root cause

glob@10.5.0 is brought in through:

@aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.

Proposed fix

Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:

  • npm install completes with zero deprecation warnings.
  • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
  • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.

Happy to send PRs against both main and preview branches if this approach is acceptable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
       blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

      Skip to content
      npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
      Closed
      #1008
      Closed
      npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
      #1008
      Description
      @minorun365
      minorun365
      opened on Apr 29, 2026
      Description
      Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
      Steps to Reproduce
      1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
      2. Observe the warning in the output
      Expected Behavior
      npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
      Actual Behavior
      npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

      CLI Version
      • 0.12.0 (latest)
      • 1.0.0-preview.3 (preview)
      Both are affected.
      Operating System
      macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
      Additional Context
      Root cause
      glob@10.5.0 is brought in through:
      @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

      archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
      Proposed fix
      Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
      • npm install completes with zero deprecation warnings.
      • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
      • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
      Happy to send PRs against both main and preview branches if this approach is acceptable.
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        No labels
        No labels
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

          Skip to content
          npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
          Closed
          #1008
          Closed
          npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
          #1008
          Description
          @minorun365
          minorun365
          opened on Apr 29, 2026
          Description
          Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
          Steps to Reproduce
          1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
          2. Observe the warning in the output
          Expected Behavior
          npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
          Actual Behavior
          npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

          CLI Version
          • 0.12.0 (latest)
          • 1.0.0-preview.3 (preview)
          Both are affected.
          Operating System
          macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
          Additional Context
          Root cause
          glob@10.5.0 is brought in through:
          @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

          archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
          Proposed fix
          Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
          • npm install completes with zero deprecation warnings.
          • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
          • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
          Happy to send PRs against both main and preview branches if this approach is acceptable.
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            No labels
            No labels
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

              Skip to content
              npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
              Closed
              #1008
              Closed
              npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
              #1008
              Description
              @minorun365
              minorun365
              opened on Apr 29, 2026
              Description
              Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
              Steps to Reproduce
              1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
              2. Observe the warning in the output
              Expected Behavior
              npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
              Actual Behavior
              npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

              CLI Version
              • 0.12.0 (latest)
              • 1.0.0-preview.3 (preview)
              Both are affected.
              Operating System
              macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
              Additional Context
              Root cause
              glob@10.5.0 is brought in through:
              @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

              archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
              Proposed fix
              Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
              • npm install completes with zero deprecation warnings.
              • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
              • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
              Happy to send PRs against both main and preview branches if this approach is acceptable.
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                No labels
                No labels
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions
                  
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

                  Skip to content
                  npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
                  Closed
                  #1008
                  Closed
                  npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
                  #1008
                  Description
                  @minorun365
                  minorun365
                  opened on Apr 29, 2026
                  Description
                  Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
                  Steps to Reproduce
                  1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
                  2. Observe the warning in the output
                  Expected Behavior
                  npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
                  Actual Behavior
                  npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

                  CLI Version
                  • 0.12.0 (latest)
                  • 1.0.0-preview.3 (preview)
                  Both are affected.
                  Operating System
                  macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
                  Additional Context
                  Root cause
                  glob@10.5.0 is brought in through:
                  @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

                  archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
                  Proposed fix
                  Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
                  • npm install completes with zero deprecation warnings.
                  • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
                  • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
                  Happy to send PRs against both main and preview branches if this approach is acceptable.
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    No labels
                    No labels
                    Type
                    No type
                    Projects
                    No projects
                      Milestone
                      No milestone
                      Relationships
                      None yet
                      Development
                      No branches or pull requests
                      Issue actions
                      
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

                      Skip to content
                      npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
                      Closed
                      #1008
                      Closed
                      npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
                      #1008
                      Description
                      @minorun365
                      minorun365
                      opened on Apr 29, 2026
                      Description
                      Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
                      Steps to Reproduce
                      1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
                      2. Observe the warning in the output
                      Expected Behavior
                      npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
                      Actual Behavior
                      npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

                      CLI Version
                      • 0.12.0 (latest)
                      • 1.0.0-preview.3 (preview)
                      Both are affected.
                      Operating System
                      macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
                      Additional Context
                      Root cause
                      glob@10.5.0 is brought in through:
                      @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

                      archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
                      Proposed fix
                      Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
                      • npm install completes with zero deprecation warnings.
                      • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
                      • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
                      Happy to send PRs against both main and preview branches if this approach is acceptable.
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        No labels
                        No labels
                        Type
                        No type
                        Projects
                        No projects
                          Milestone
                          No milestone
                          Relationships
                          None yet
                          Development
                          No branches or pull requests
                          Issue actions
                          
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

                          Skip to content
                          npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
                          Closed
                          #1008
                          Closed
                          npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
                          #1008
                          Description
                          @minorun365
                          minorun365
                          opened on Apr 29, 2026
                          Description
                          Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
                          Steps to Reproduce
                          1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
                          2. Observe the warning in the output
                          Expected Behavior
                          npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
                          Actual Behavior
                          npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

                          CLI Version
                          • 0.12.0 (latest)
                          • 1.0.0-preview.3 (preview)
                          Both are affected.
                          Operating System
                          macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
                          Additional Context
                          Root cause
                          glob@10.5.0 is brought in through:
                          @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

                          archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
                          Proposed fix
                          Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
                          • npm install completes with zero deprecation warnings.
                          • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
                          • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
                          Happy to send PRs against both main and preview branches if this approach is acceptable.
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            No labels
                            No labels
                            Type
                            No type
                            Projects
                            No projects
                              Milestone
                              No milestone
                              Relationships
                              None yet
                              Development
                              No branches or pull requests
                              Issue actions
                              
, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

                              Skip to content
                              npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils) #1007
                              Closed
                              #1008
                              Closed
                              npm install emits deprecation warning for glob@10.5.0 (transitive via archiver-utils)#1007
                              #1008
                              Description
                              @minorun365
                              minorun365
                              opened on Apr 29, 2026
                              Description
                              Running npm install -g @aws/agentcore emits an npm deprecation warning about glob@10.5.0, which is pulled in transitively through archiver-utils@5.0.2. The install itself succeeds, but the warning adds noise to the user's first interaction with the CLI and may cause concern for users sensitive to deprecation/security signals.
                              Steps to Reproduce
                              1. npm install -g @aws/agentcore (or npm install in a fresh clone of this repo)
                              2. Observe the warning in the output
                              Expected Behavior
                              npm install completes without deprecation warnings, since the underlying issue has a supported successor available (glob@>=12).
                              Actual Behavior
                              npm warn deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me

                              CLI Version
                              • 0.12.0 (latest)
                              • 1.0.0-preview.3 (preview)
                              Both are affected.
                              Operating System
                              macOS (also reproducible on Linux/Windows — the warning originates from a transitive npm dependency)
                              Additional Context
                              Root cause
                              glob@10.5.0 is brought in through:
                              @aws/agentcore
├─ @aws-cdk/toolkit-lib
└─ archiver@7.0.1
└─ archiver-utils@5.0.2 ← still pins "glob": "^10.0.0" (latest version)
└─ glob@10.5.0 (deprecated)

                              archiver-utils@latest (5.0.2) still requires glob@^10.0.0, so this cannot be fixed at the source. On the npm registry, glob@<12 is currently marked as deprecated (legacy-v10 and earlier dist-tags); only glob@>=12 is free of the warning.
                              Proposed fix
                              Pin glob to ^13.0.0 (current latest) via package.json#overrides, following the same pattern already used in this repo for minimatch, fast-xml-parser, and @aws-sdk/xml-builder. Verified locally:
                              • npm install completes with zero deprecation warnings.
                              • archiver-utils@5.0.2 only uses glob.sync(pattern, options), which remains a stable API in glob@13.
                              • glob@13's own minimatch ^10.2.2 requirement is compatible with the existing minimatch: 10.2.4 override.
                              Happy to send PRs against both main and preview branches if this approach is acceptable.
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                No labels
                                No labels
                                Type
                                No type
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions