dart-resolve-package-conflicts
Resolve Dart Package Conflicts Safely
Dart package conflicts can block builds and make upgrades difficult. This skill provides a controlled workflow to inspect constraints, update dependencies, and verify the resolved graph.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "dart-resolve-package-conflicts" from https://skillstore.io/skills/flutter-dart-resolve-package-conflicts.md and its manifest at https://skillstore.io/api/skills/flutter-dart-resolve-package-conflicts/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「dart-resolve-package-conflicts」を使用しています。 A project cannot resolve http because direct and transitive constraints are incompatible.
期待される結果:
- Identify the direct constraint and the package imposing the transitive constraint.
- Check whether a compatible http version exists.
- Update the smallest necessary constraint, then run dependency checks and tests.
「dart-resolve-package-conflicts」を使用しています。 dart pub outdated shows a resolvable minor update.
期待される結果:
- The update needs a pubspec.yaml constraint change.
- Apply the new compatible lower bound.
- Run dart pub upgrade, dart analyze, and dart test before committing the lockfile.
セキュリティ監査
安全All 37 external-command alerts are false positives caused by Markdown backticks around documented Dart commands, file names, and code examples. The single network alert is a standard pub.dev URL in a lockfile example, not an active request. No prompt-injection, exfiltration, or malicious intent was found.
リスク要因
⚙️ 外部コマンド (37)
🌐 ネットワークアクセス (1)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/flutter-dart-resolve-package-conflicts/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/flutter-dart-resolve-package-conflicts?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/flutter-dart-resolve-package-conflicts?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/flutter-dart-resolve-package-conflicts/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/flutter-dart-resolve-package-conflicts.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
flutter. (2026). dart-resolve-package-conflicts security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/flutter-dart-resolve-package-conflicts/audits/1BibTeX形式の引用
@techreport{flutter-flutter-dart-resolve-package-conflicts-2026,
author = {flutter},
title = {dart-resolve-package-conflicts security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/flutter-dart-resolve-package-conflicts/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "dart-resolve-package-conflicts security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "flutter"
date-released: "2026-08-30"
url: "https://skillstore.io/skills/flutter-dart-resolve-package-conflicts/audits/1"
identifiers:
- type: other
value: "skillstore:flutter-dart-resolve-package-conflicts:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Unblock a Flutter build
Identify incompatible dependency constraints after dart pub get fails and select a narrow resolution path.
Plan a controlled upgrade
Use outdated-package results to separate safe compatible updates from changes that require new constraints.
Stabilize CI dependencies
Apply lockfile and verification practices to keep tested package versions consistent in continuous integration.
これらのプロンプトを試す
Explain this dart pub get version-solving error in simple terms and list the first checks I should make.
Review this dart pub outdated output. Separate packages that are upgradable from packages that need pubspec.yaml constraint changes.
Help me resolve this conflict between these pubspec.yaml constraints. Propose the smallest safe change and explain why.
Create a staged Dart dependency upgrade plan from these pubspec files and test results. Include verification after each stage.
ベストプラクティス
- Review dart pub outdated before changing version constraints.
- Change one dependency group at a time and test after each change.
- Commit pubspec.yaml and pubspec.lock together after successful verification.
回避
- Do not delete the full lockfile to bypass a single conflict.
- Do not upgrade every dependency before identifying the constraint causing the failure.
- Do not ignore analyzer or test failures after a dependency upgrade.