'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

Set up dependency-cruiser in a TypeScript repository to enforce package boundaries: outside code uses public entry files while implementation stays in subfolders. Add checks, a starter package, and documentation, then verify that forbidden imports fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preventing imports into package internals
• Adding boundary checks to existing validation commands
• Creating a starter package with public entry files

Move NuGet package versions from individual .NET projects into a shared management file. The skill audits version conflicts, preserves project conditions, validates builds before and after conversion, and produces comparison files and a migration report.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adopting central NuGet package version management
• Aligning inconsistent package versions across projects
• Moving shared version properties into central declarations

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Remove an installed UPM package, a package managed by Unity, from a project. Checks that it exists, updates manifest.json, and delivers the result after any reload. Built-in packages and dependencies of other packages cannot be removed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Remove an unused package from a Unity project
• Check whether a package is installed before removal
• Receive removal results after Unity finishes reloading

Add packages to a Unity project from its package registry, a Git URL, or a local path. Choose a compatible version or specify one, and receive the installation result after any required reload.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Installing a Unity registry package
• Adding a package at a specific version
• Installing from a Git branch or tag

Manage Python and R packages for notebook work. Resolve missing-package errors, check installed versions, install into the selected runtime, and restart the kernel when needed, with guidance on using separate environments for different dependency requirements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Resolve missing-package errors in a notebook
• Check installed package versions
• Separate project dependencies into a named environment

Migrate legacy .NET project files to SDK-style format, reducing repetitive XML and explicit file lists. Convert package references, move assembly metadata into project settings, and consolidate shared build and package settings across multiple projects.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Convert legacy .csproj or .vbproj files to SDK-style
• Migrate packages.config to PackageReference
• Replace AssemblyInfo.cs with generated assembly metadata

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

Create .NET projects from templates and align them with neighboring projects and centralized package versions. Validate options, connect projects in a solution, and build the result to check that the generated structure works.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a new .NET application from a template
• Combining an API, tests, and a library in one solution
• Adding a new project with centralized package versions

Search Unity's package registry and installed packages by name, ID, or description. Review available versions and installation status before adding a package, using cached results or online lookups for exact matches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding a package by part of its name
• Searching descriptions for rendering packages
• Checking available versions and installation status

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