“package”的搜索结果

Find npm and PyPI packages that imitate trusted package names to exploit typing mistakes. Compare spelling similarity, publication dates, downloads, and maintainer details, then rank suspicious candidates and produce reports or blocklists for further review.

中文简介正在准备中。当前显示英语简介。

• Auditing project dependencies for misleading package names
• Monitoring names similar to important packages
• Investigating a suspected misspelled package installation

Use when a subscriber admin is installing, upgrading, or rolling back a managed package (1GP or 2GP) sourced from AppExchange or a private install URL — covers pre-install evaluation, sandbox dry runs, license and dependency checks, the install/upgrade audit trail, post-install configuration the package's InstallHandler cannot perform, and uninstall fallback. NOT for building managed packages as an ISV (use devops/managed-package-development), unlocked-package development (use devops/unlocked-package-development), or AppExchange listing setup. Trigger keywords: InstalledPackage, installedPackages, securityType, activateRSS, sf package install, sf package installed list, PackageLicense, UserPackageLicense, AllowedLicenses, UsedLicenses, push upgrade, PackageSubscriber, namespace prefix, 04t, certified managed package limits.

中文简介正在准备中。当前显示原文说明。

Manage MATLAB packages with the in-product MATLAB Package Manager (mpm) on MATLAB R2026b or later: install, uninstall, update, search, or inspect packages; declare package dependencies in a matlab.toml project; install a shareable .mltbx package; or manage repositories. Covers dependency-resolution errors and anything involving mpminstall / mpmuninstall / mpmupdate / mpmlist / mpmsearch / mpmAddRepository / matlab.mpm.*. MATLAB *packages* are distinct from MathWorks products, toolboxes, and support packages: a bare "what packages are installed?" means MPM packages (mpmlist / matlab.mpm.Package) — this skill — unless the user explicitly says products, toolboxes, or support packages. NOT for installing MATLAB, Simulink, or toolboxes from a shell via the standalone mpm executable (the OS-level product installer), nor for listing installed products / toolboxes (ver, installedAddons) — use matlab-install-products for those.

中文简介正在准备中。当前显示原文说明。

Guide substantial Swift changes in cmux with rules for package boundaries, dependency direction, state management, concurrency, and API documentation. Structure code so public package types can be tested without launching the app.

中文简介正在准备中。当前显示英语简介。

• Extracting a large app feature into Swift Packages
• Reviewing dependencies between UI, domain models, and services
• Restructuring state management and Swift 6 concurrency

npm package maintenance and lifecycle management for monorepo extensions. Covers health audits, dependency sync, version bumping, changelog updates, pre-publish checks, coordinated publishing, and post-publish verification. **Triggers — use this skill when:** - User asks to "publish", "release", or "version bump" extensions/packages - User says "audit packages", "check package health", "dependency sync" - User asks to "update changelogs", "prepare release", "pre-publish check" - User mentions "npm publish", "version management", "package lifecycle" - User wants to "sync dependencies" or "align versions" across packages - User asks "what needs publishing" or "which packages changed" **Covers:** Monorepo with multiple npm packages under `extensions/`. Each package has its own package.json, CHANGELOG.md, README.md, and version. Packages are scoped (e.g. `@e9n/pi-*`) and published individually.

中文简介正在准备中。当前显示原文说明。

Detects typosquatting attacks in npm and PyPI package registries by analyzing package name similarity using Levenshtein distance and other string metrics, examining publish date heuristics to identify recently created packages mimicking established ones, and flagging download count anomalies where suspicious packages have disproportionately low usage compared to their legitimate targets. The analyst queries the PyPI JSON API and npm registry API to gather package metadata for automated comparison. Activates for requests involving package typosquatting detection, dependency confusion analysis, malicious package identification, or software supply chain threat hunting in package registries.

中文简介正在准备中。当前显示原文说明。

Inspect npm packages and dependency files for malicious installation scripts, credential theft, and self-spreading behavior. Use GuardDog scanning, source inspection, known-malicious version checks, and isolated execution to produce an evidence-based assessment.

中文简介正在准备中。当前显示英语简介。

• Vetting a new npm dependency before adoption
• Reviewing dependency files during code review
• Checking lockfiles against known-malicious versions

Find dependency confusion risks, where a public package can replace an internal package with the same name. Review dependency files, identify exposed names, and guide registry restrictions and recurring CI checks to prevent substitution.

中文简介正在准备中。当前显示英语简介。

• Auditing projects that mix private and public package registries
• Checking exposure after internal package names have leaked
• Restricting package sources to approved private registries

Package a CARLA server built with UE 5.8 for distribution, choosing which maps to include. Inspect the resulting files for mismatched containers, missing road data, and exposure settings that can cause runtime failures.

中文简介正在准备中。当前显示英语简介。

• Packaging a CARLA server with selected maps
• Investigating a black screen in a packaged server
• Checking road data and package consistency

Build distributable CARLA releases or asset packages containing selected maps and props. It prepares content for runtime use, checks output files, supports destination changes, and preserves native ROS 2 support when explicitly enabled.

中文简介正在准备中。当前显示英语简介。

• Create a full CARLA release archive
• Export Town02 as an importable asset package
• Preserve native ROS 2 support in a packaged build

Assess dependency confusion, where a build retrieves a public package instead of an intended private one. Discover internal package names, review registry settings, plan callback-based proofs of execution, and document fixes across major package ecosystems.

中文简介正在准备中。当前显示英语简介。

• Reviewing package registry settings in CI/CD
• Finding internal package names in lock files
• Planning an authorized callback-based proof of concept

Build, run, and test macOS Swift packages using SwiftPM, the Swift package manager. Identifies available libraries and executables, selects relevant commands and tests, and reports results with the main blocker when something fails.

中文简介正在准备中。当前显示英语简介。

• Build a package without an Xcode project
• Choose and run an executable product
• Run a specific test target or case

Windows アプリ開発 (MSIX / Microsoft Store) のパッケージング・配置・公開リファレンス。 MSIX, MSIX Core, AppxManifest, MakeAppx, MSIX Packaging Tool, パッケージボリューム, Package Bundles, App Attach, PSF (Package Support Framework), Package Identity, PackageFamilyName, スパースパッケージ, App Installer, サイドローディング, PackageManager, Windows App SDK Bootstrapper, 自己完結型デプロイ, SignTool, 証明書, Azure Trusted Signing (Azure Artifact Signing), CI/CD 署名, GitHub Actions, msstore CLI, Partner Center ロール, アプリ送信, ストアリスティング, 年齢レーティング, 認定プロセス, 段階的ロールアウト, StoreContext, 分析レポート。

中文简介正在准备中。当前显示原文说明。

Find npm packages that help implement or check a frontend rule, verify download counts and publishing dates, and add up to three qualifying package names to the rule file's metadata.

中文简介正在准备中。当前显示英语简介。

• Adding npm package references to checklist rules
• Screening packages by downloads and publishing dates
• Finding tools to detect, fix, or test a rule

Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.

中文简介正在准备中。当前显示英语简介。

• Creating a new @remotion package
• Registering a package across the monorepo
• Adding documentation and usage examples

Manage NuGet packages, the libraries used by .NET projects, through consistent add, remove, and update procedures. Check that requested versions exist, locate their configuration, and run dependency restoration to check for errors after updates.

中文简介正在准备中。当前显示英语简介。

• Add a NuGet package to a .NET project
• Remove an unused package
• Update a package version across a solution

Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.

中文简介正在准备中。当前显示英语简介。

• Adding a public SDK feature or export
• Renaming public types while preserving compatibility
• Changing streaming or transport behavior

View and interact with an iOS Simulator inside the Codex browser. Display SwiftUI previews from importable Swift packages, see source edits update the running preview, and capture screenshots to document the visible results.

中文简介正在准备中。当前显示英语简介。

• Viewing and interacting with an iOS app in the browser
• Checking SwiftUI previews outside Xcode Canvas
• Iterating on package previews with hot reload

MUST use for ANY query mentioning packages, monorepo, workspace, catalog, turbo, turborepo, or pnpm in a multi-package context. MUST use when sharing config (ESLint, tsconfig, prettier) across packages, fixing build order between packages, adding new packages, scoping CI installs/caching to changed packages, or debugging pnpm catalog version resolution. This skill OWNS all cross-package coordination problems — even when they look like build, CI, config, or dependency issues. If two or more packages interact in the query, this skill applies. Takes priority over other skills when the problem spans package boundaries.

中文简介正在准备中。当前显示原文说明。

Find Laravel packages for specific features through LaraPlugins.io MCP, a connection to its package search tools. Check maintenance indicators, release history, and Laravel/PHP compatibility to compare candidates before adding a package to a project.

中文简介正在准备中。当前显示英语简介。

• Find packages for authentication or permission management
• Find admin panel packages
• Check whether a package is actively maintained

Manage multiple apps and shared packages in one repository. Analyze dependencies and change impacts, limit builds and tests to affected packages, configure caching, and plan repository consolidation while preserving Git history.

中文简介正在准备中。当前显示英语简介。

• Checking which apps a shared package change affects
• Limiting CI builds and tests to affected packages
• Combining repositories while preserving Git history

Manage FrontendExtension resources in frontend-forge, from creation and package generation to downloading, publishing, and unpublishing. Inspect generated files, Kubernetes jobs, and status information to diagnose packaging or publishing failures.

中文简介正在准备中。当前显示英语简介。

• Create or update a FrontendExtension
• Rebuild and download an extension package
• Publish, unpublish, or remove an extension

Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.

中文简介正在准备中。当前显示原文说明。

Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.

中文简介正在准备中。当前显示原文说明。