@builder.io/dev-tools
Builder.io Visual CMS Devtools
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): Phantom dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:ignore | AI (phantom-deps): Phantom dep pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Phantom dep pattern is stable for this package; deps referenced via config conventions. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Automated CI/CD pipeline for a high-velocity package (2460 versions); rapid successive publishes are expected. | ai | |
| provenance | publisher-changed | AI (provenance): Builder.io migrated publishing to GitHub Actions CI; consistent with org-level automation across their many packages. | ai | |
| source-diff | obfuscated-file:types/cli/utils/repo-indexing-group-prompts.d.ts | AI (source-diff): Long-line .d.ts file contains a readable LLM prompt string constant, not obfuscated/minified code. | ai | |
| dependencies | unvetted-dep:http-proxy | AI (dependencies): http-proxy is a well-established library; stable dependency for this package across many versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): zod is a well-established validation library; addition is benign for this package. | ai | |
| source-diff | obfuscated-file:types/cli/utils/repo-indexing-agent-prompt.d.ts | AI (source-diff): Same pattern — exported prompt template string in a .d.ts file, not obfuscation. | ai | |
| source-diff | obfuscated-file:types/cli/utils/component-group-mdx-prompt.d.ts | AI (source-diff): Long-line .d.ts files are LLM prompt string constants, not obfuscated code; pattern stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Large org package with frequent releases; new maintainer addition consistent with team growth, not compromise. | ai | |
| phantom-deps | phantom-dep:http-proxy-middleware | AI (phantom-deps): Proxy middleware is a documented feature; dynamic loading pattern is expected for this dev-tools package. | ai | |
| phantom-deps | phantom-dep:@vscode/ripgrep | AI (phantom-deps): IDE integration dep; conditionally loaded in dev-tools context, not a direct import. | ai | |
| phantom-deps | phantom-dep:http-proxy | AI (phantom-deps): Proxy functionality is a documented feature of this dev-tools package; dynamic loading pattern is expected. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Dev-tools package; express is a peer/optional runtime dep loaded dynamically, not a direct import. | ai | |
| provenance | no-provenance | AI (provenance): Established package; provenance is a best-practice enhancement, not a security blocker. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Same context as hex-decode — dotenv parsing code, not malicious payload handling. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Sample shows dotenv escape sequence parsing (\r, \n handling), not malicious payload decoding. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Bundled dotenv/config library code reading process.env keys — standard behavior for a dev-tools package that manages environment configuration. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): Same rationale as child-process-import — legitimate dev-tools usage for spawning build/CLI processes. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Dev-tools package legitimately spawns child processes for build tooling, CLI commands. Bundled minified code context shows standard tooling usage, not malicious behavior. | ai | |
| phantom-deps | phantom-dep:tsx | AI (phantom-deps): tsx is a common TypeScript execution tool referenced in dev-tools config files; phantom-dep pattern is expected for this package type. | ai | |
| dependencies | unvetted-dep:@lvce-editor/ripgrep | AI (dependencies): @lvce-editor/ripgrep is a ripgrep binary wrapper appropriate for a dev-tools package doing file search; its use is consistent with the package's purpose. | ai | |
| phantom-deps | phantom-dep:http-proxy-3 | AI (phantom-deps): http-proxy-3 referenced in config files for dev server proxying is expected behavior for a dev-tools package. | ai | |
| phantom-deps | phantom-dep:@lvce-editor/ripgrep | AI (phantom-deps): Consistent with the dependency finding; conditionally loaded in config, appropriate for dev-tools file search functionality. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only package loaded by convention in dev-tools context; not a security concern. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:@amplitude/analytics-node | AI (dependencies): Official Amplitude analytics SDK; standard telemetry dependency for dev tools. Legitimate use. | ai | |
| dependencies | unvetted-dep:launch-editor | AI (dependencies): launch-editor is a well-known utility used by major dev tools (Vue CLI, CRA) to open files in editors; legitimate use in dev-tools context. | ai | |
| phantom-deps | phantom-dep:@tootallnate/quickjs-emscripten | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:utf-8-validate | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:@clack/prompts | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:cookie-parser | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:pac-resolver | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:cli-progress | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:detect-port | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:bufferutil | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:get-port | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): Dev-tools package; phantom deps are config-referenced optional/conditional imports, not a security concern for this package. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled binaries are ripgrep (rg/rg.exe) — a well-known open-source search tool. Bundling platform-specific ripgrep binaries is a standard pattern for dev tools requiring fast file search. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() in bundled CJS output is a common pattern in transpiled/bundled JavaScript frameworks. No evidence of malicious intent in the code samples. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Appears in bundled/minified CJS output (node/index.cjs). Code context shows template literal parsing (Babel/parser internals), not dynamic code execution of untrusted input. | ai |
Versions (showing 100 of 514)
| Version | Deps | Published |
|---|---|---|
| 1.26.3 | 26 / 4 | |
| 1.26.2 | 26 / 4 | |
| 1.26.1 | 26 / 4 | |
| 1.26.0 | 26 / 4 | |
| 1.25.0 | 24 / 4 | |
| 1.24.0 | 24 / 4 | |
| 1.23.3 | 24 / 4 | |
| 1.23.2 | 24 / 4 | |
| 1.23.1 | 24 / 4 | |
| 1.23.0 | 24 / 4 | |
| 1.22.6 | 24 / 4 | |
| 1.22.4 | 24 / 4 | |
| 1.22.3 | 24 / 4 | |
| 1.22.2 | 24 / 4 | |
| 1.22.1 | 24 / 4 | |
| 1.21.16 | 24 / 4 | |
| 1.21.15 | 24 / 4 | |
| 1.21.14 | 24 / 4 | |
| 1.21.12 | 24 / 4 | |
| 1.21.11 | 24 / 4 | |
| 1.21.10 | 24 / 4 | |
| 1.21.9 | 24 / 4 | |
| 1.21.8 | 24 / 4 | |
| 1.21.7 | 24 / 4 | |
| 1.21.6 | 24 / 4 | |
| 1.21.5 | 24 / 4 | |
| 1.21.4 | 24 / 4 | |
| 1.21.3 | 24 / 4 | |
| 1.21.2 | 24 / 4 | |
| 1.21.1 | 24 / 4 | |
| 1.21.0 | 24 / 4 | |
| 1.20.1 | 24 / 4 | |
| 1.20.0 | 24 / 4 | |
| 1.19.14 | 24 / 4 | |
| 1.19.13 | 24 / 4 | |
| 1.19.12 | 24 / 4 | |
| 1.19.11 | 24 / 4 | |
| 1.19.10 | 24 / 4 | |
| 1.19.9 | 24 / 4 | |
| 1.19.8 | 24 / 4 | |
| 1.19.7 | 24 / 4 | |
| 1.19.6 | 24 / 4 | |
| 1.19.5 | 24 / 4 | |
| 1.19.4 | 24 / 4 | |
| 1.19.3 | 24 / 4 | |
| 1.19.2 | 24 / 4 | |
| 1.19.1 | 24 / 4 | |
| 1.19.0 | 24 / 4 | |
| 1.18.50 | 24 / 4 | |
| 1.18.49 | 24 / 4 | |
| 1.18.48 | 24 / 4 | |
| 1.18.47 | 24 / 4 | |
| 1.18.46 | 24 / 4 | |
| 1.18.45 | 24 / 4 | |
| 1.18.44 | 24 / 4 | |
| 1.18.43 | 24 / 4 | |
| 1.18.42 | 24 / 4 | |
| 1.18.41 | 24 / 4 | |
| 1.18.40 | 24 / 4 | |
| 1.18.39 | 24 / 4 | |
| 1.18.38 | 24 / 4 | |
| 1.18.37 | 24 / 4 | |
| 1.18.36 | 25 / 4 | |
| 1.18.35 | 26 / 3 | |
| 1.18.34 | 26 / 3 | |
| 1.18.33 | 26 / 3 | |
| 1.18.31 | 26 / 3 | |
| 1.18.30 | 26 / 3 | |
| 1.18.28 | 26 / 3 | |
| 1.18.27 | 26 / 3 | |
| 1.18.26 | 26 / 3 | |
| 1.18.25 | 26 / 3 | |
| 1.18.24 | 26 / 3 | |
| 1.18.23 | 26 / 3 | |
| 1.18.22 | 26 / 3 | |
| 1.18.21 | 26 / 3 | |
| 1.18.20 | 26 / 3 | |
| 1.18.19 | 26 / 3 | |
| 1.18.18 | 26 / 3 | |
| 1.18.17 | 26 / 3 | |
| 1.18.16 | 26 / 3 | |
| 1.18.15 | 26 / 3 | |
| 1.18.14 | 26 / 3 | |
| 1.18.13 | 26 / 3 | |
| 1.18.12 | 26 / 3 | |
| 1.18.11 | 26 / 3 | |
| 1.18.10 | 26 / 3 | |
| 1.18.9 | 26 / 3 | |
| 1.18.8 | 26 / 3 | |
| 1.18.7 | 26 / 3 | |
| 1.18.6 | 26 / 3 | |
| 1.18.5 | 26 / 3 | |
| 1.18.4 | 26 / 3 | |
| 1.18.3 | 26 / 3 | |
| 1.18.1 | 26 / 3 | |
| 1.18.0 | 26 / 3 | |
| 1.17.31 | 26 / 3 | |
| 1.17.30 | 26 / 3 | |
| 1.17.29 | 26 / 3 | |
| 1.17.28 | 26 / 3 |
v1.26.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.6
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.3
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.16
2 findingsThis version was published by a different npm account than previous versions on 2026-01-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.15
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.14
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.12
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.11
2 findingsThis version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.9
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.8
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.7
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.6
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.5
2 findingsThis version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-19. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.14
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.13
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.12
2 findingsThis version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.11
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.9
2 findingsThis version was published by a different npm account than previous versions on 2025-12-31. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.8
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.7
2 findingsThis version was published by a different npm account than previous versions on 2025-12-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.6
2 findingsThis version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.5
2 findingsThis version was published by a different npm account than previous versions on 2025-12-22. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.4
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
2 findingsThis version was published by a different npm account than previous versions on 2025-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
2 findingsThis version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.50
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.49
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.48
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.47
2 findingsThis version was published by a different npm account than previous versions on 2025-12-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.46
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.45
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.44
2 findingsThis version was published by a different npm account than previous versions on 2025-12-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.43
2 findingsThis version was published by a different npm account than previous versions on 2025-12-10. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.42
2 findingsThis version was published by a different npm account than previous versions on 2025-12-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.