workbox-precaching
This module efficiently precaches assets.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.dev.v2.1.0.js | AI (source-diff): Minified build artifact from Google's Workbox build pipeline; Apache 2.0 license header present, source maps included, content is legitimate service worker precaching code. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.prod.v2.1.0.mjs | AI (source-diff): Minified ESM production build artifact from Google's Workbox build pipeline; Apache 2.0 license header present, source maps included, content is legitimate service worker precaching code. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.dev.v2.1.0.mjs | AI (source-diff): Minified ESM build artifact from Google's Workbox build pipeline; Apache 2.0 license header present, source maps included, content is legitimate service worker precaching code. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.prod.v2.1.0.js | AI (source-diff): Minified production build artifact from Google's Workbox build pipeline; Apache 2.0 license header present, source maps included, content is legitimate service worker precaching code. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.dev.v2.0.2-rc1-2.0.2-rc1.0.mjs | AI (source-diff): Standard minified ES module build artifact produced by gulp build for the official Google Workbox library. Apache 2.0 header present; content is legitimate service worker caching code. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.prod.v2.0.2-rc1-2.0.2-rc1.0.js | AI (source-diff): Standard minified build artifact produced by gulp build for the official Google Workbox library. Apache 2.0 header present; content is legitimate service worker caching code. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.dev.v2.0.2-rc1-2.0.2-rc1.0.js | AI (source-diff): Standard minified build artifact produced by gulp build for the official Google Workbox library. Apache 2.0 header present; content is legitimate service worker caching code. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.prod.v2.0.2-rc1-2.0.2-rc1.0.mjs | AI (source-diff): Standard minified ES module build artifact produced by gulp build for the official Google Workbox library. Apache 2.0 header present; content is legitimate service worker caching code. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.prod.v2.0.3.mjs | AI (source-diff): Standard minified ESM build artifact from Google's Workbox project. Apache-licensed, workbox-specific caching logic, no malicious content. Minification is expected for this package. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.dev.v2.0.3.js | AI (source-diff): Standard minified build artifact from Google's Workbox project. Apache-licensed, workbox-specific caching logic, no malicious content. Minification is expected for this package. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.prod.v2.0.3.js | AI (source-diff): Standard minified build artifact from Google's Workbox project. Apache-licensed, workbox-specific caching logic, no malicious content. Minification is expected for this package. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.dev.v2.0.3.mjs | AI (source-diff): Standard minified ESM build artifact from Google's Workbox project. Apache-licensed, workbox-specific caching logic, no malicious content. Minification is expected for this package. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.prod.v1.3.0.mjs | AI (source-diff): Standard minified production ESM build artifact from Workbox's gulp build pipeline; declared as package module entry point. Pattern is stable for this package. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.dev.v1.3.0.js | AI (source-diff): Standard minified build artifact from Workbox's gulp build pipeline; Google copyright header and workbox-specific logic confirm legitimacy. Pattern is stable for this package. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.dev.v1.3.0.mjs | AI (source-diff): Standard minified ESM build artifact from Workbox's gulp build pipeline; Google copyright header and workbox-specific logic confirm legitimacy. Pattern is stable for this package. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.prod.v1.3.0.js | AI (source-diff): Standard minified production build artifact from Workbox's gulp build pipeline; declared as package main entry point. Pattern is stable for this package. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.prod.v2.0.0.mjs | AI (source-diff): Standard minified ES module production build artifact from Google's Workbox project; Apache 2.0 licensed, accompanied by source maps, contains only service worker caching logic. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.dev.v2.0.0.js | AI (source-diff): Standard minified build artifact from Google's Workbox project; Apache 2.0 licensed, accompanied by source maps, contains only service worker caching logic. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.prod.v2.0.0.js | AI (source-diff): Standard minified production build artifact from Google's Workbox project; Apache 2.0 licensed, accompanied by source maps, contains only service worker caching logic. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.dev.v2.0.0.mjs | AI (source-diff): Standard minified ES module build artifact from Google's Workbox project; Apache 2.0 licensed, accompanied by source maps, contains only service worker caching logic. | ai | |
| source-diff | obfuscated-file:build/workbox-precaching.prod.js | AI (source-diff): Production build artifact (minified browser JS) for a Google Workbox library. The code is clearly a service worker precaching implementation with no malicious patterns. Expected for this package type. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): workbox-core is the official shared core of the Workbox ecosystem, published by the same Google team. Adding it as a dependency in v4.0.0 is part of the documented modular refactor. | ai | |
| source-diff | large-new-source-files | AI (source-diff): v4.0.0 was a major architectural rewrite of Workbox; new source files are expected and consistent with the legitimate release history. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.dev.v1.2.0.js | AI (source-diff): workbox-precaching ships minified build bundles as its primary distribution format; these are standard bundler outputs with Apache 2.0 headers, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.prod.v1.2.0.mjs | AI (source-diff): workbox-precaching ships minified build bundles as its primary distribution format; these are standard bundler outputs with Apache 2.0 headers, not malicious obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; no-provenance is expected for this vintage Google package. | ai | |
| source-diff | obfuscated-file:build/modules/workbox-precaching.dev.v1.2.0.mjs | AI (source-diff): workbox-precaching ships minified build bundles as its primary distribution format; these are standard bundler outputs with Apache 2.0 headers, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:build/importScripts/workbox-precaching.prod.v1.2.0.js | AI (source-diff): workbox-precaching ships minified build bundles as its primary distribution format; these are standard bundler outputs with Apache 2.0 headers, not malicious obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of snugug alongside addition of tomayac reflects a routine maintainer handoff within Google's Workbox team, not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): tomayac is a known Google engineer; addition is consistent with legitimate team transition within the GoogleChrome/workbox project. | ai | |
| provenance | publisher-changed | AI (provenance): tomayac is a known Google DevRel engineer; transition from tropicadri to tomayac is consistent with internal Google team rotation for the Workbox project. | ai |
Versions (showing 61 of 61)
| Version | Deps | Published |
|---|---|---|
| 7.4.1 | 3 / 0 | |
| 7.3.0 | 3 / 0 | |
| 7.1.0 | 3 / 0 | |
| 7.0.0 | 3 / 0 | |
| 6.6.1 | 3 / 0 | |
| 6.6.0 | 3 / 0 | |
| 6.5.4 | 3 / 0 | |
| 6.5.3 | 3 / 0 | |
| 6.5.2 | 3 / 0 | |
| 6.5.1 | 3 / 0 | |
| 6.5.0 | 3 / 0 | |
| 6.4.2 | 3 / 0 | |
| 6.4.1 | 3 / 0 | |
| 6.4.0 | 3 / 0 | |
| 6.3.0 | 3 / 0 | |
| 6.2.4 | 3 / 0 | |
| 6.2.3 | 3 / 0 | |
| 6.2.2 | 3 / 0 | |
| 6.2.1 | 3 / 0 | |
| 6.2.0 | 3 / 0 | |
| 6.1.5 | 3 / 0 | |
| 6.1.2 | 3 / 0 | |
| 6.1.1 | 3 / 0 | |
| 6.1.0 | 3 / 0 | |
| 6.0.2 | 3 / 0 | |
| 6.0.0 | 3 / 0 | |
| 5.1.4 | 1 / 0 | |
| 5.1.3 | 1 / 0 | |
| 5.1.2 | 1 / 0 | |
| 5.1.1 | 1 / 0 | |
| 5.1.0 | 1 / 0 | |
| 5.0.0 | 1 / 0 | |
| 4.3.1 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.1 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.0 | 1 / 0 | |
| 3.6.3 | 1 / 0 | |
| 3.6.2 | 1 / 0 | |
| 3.6.1 | 1 / 0 | |
| 3.6.0 | 1 / 0 | |
| 3.5.0 | 1 / 0 | |
| 3.4.1 | 1 / 0 | |
| 3.3.1 | 1 / 0 | |
| 3.3.0 | 1 / 0 | |
| 3.2.0 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 3.0.1 | 1 / 0 | |
| 3.0.0 | 1 / 0 | |
| 2.1.0 | 0 / 2 | |
| 2.0.3 | 0 / 2 | |
| 2.0.2 | 0 / 2 | |
| 2.0.0 | 0 / 2 | |
| 1.3.0 | 0 / 2 | |
| 1.2.0 | 0 / 2 | |
| 1.1.0 | 0 / 2 | |
| 1.0.0 | 0 / 2 | |
| 0.0.3 | 0 / 2 | |
| 0.0.2 | 0 / 2 | |
| 0.0.1 | 0 / 2 |
v7.4.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v7.3.0
2 findingsThis version was published by a different npm account than previous versions on 2024-10-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-24. This could indicate a legitimate maintainer transition or an account compromise.
v6.5.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-03. This could indicate a legitimate maintainer transition or an account compromise.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-15. This could indicate a legitimate maintainer transition or an account compromise.
v6.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-11-03. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-01-29. This could indicate a legitimate maintainer transition or an account compromise.
v4.3.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-05-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-15. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-07. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-27. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-19. This could indicate a legitimate maintainer transition or an account compromise.
v3.6.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-19. This could indicate a legitimate maintainer transition or an account compromise.
v3.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-22. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-03-13. This could indicate a legitimate maintainer transition or an account compromise.
v2.1.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-08-24. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.