`intl:any` permits any available version during initial resolution
Source references: 4The Skill explicitly adds `intl:any` without a version boundary. If no lockfile exists, or the lockfile is refreshed, the resolved version depends on what the package source offers at that time rather than a compatibility range reviewed by the Skill.
The project may receive a newer version not validated by this Skill, changing build or runtime behavior and making the dependency set harder to reproduce from configuration alone. The evidence does not show a malicious package, credential access, or an actual attack.
This is an active setup command, not a warning example: it adds `intl` with the unbounded `any` constraint. During first resolution, when no lockfile exists, or when the lockfile is refreshed, Pub may select any version then compatible with the remaining constraints. This reduces reproducibility and can introduce behavior from a release the Skill did not review. The dependency is relevant to the stated localization purpose, so this is not evidence of unauthorized scope. Users can ask for a tested version range and retain and review `pubspec.lock` and resolved dependency changes.
flutter pub add flutter_localizations --sdk=flutterflutter pub add intl:any```Show 3 other places
sdk: flutter flutter_localizations: sdk: flutter intl: any```name: flutter-setup-localizationdescription: Add `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, and create an `l10n.yaml` configuration file. Use when initializing localization support for a new Flutter project.metadata:### 1. Add DependenciesAdd the required localization packages to the project. Execute the following commands in the terminal:```bashflutter pub add flutter_localizations --sdk=flutterflutter pub add intl:any```