prisma_cli 1.0.5
prisma_cli: ^1.0.5 copied to clipboard
◭ Prisma is a modern DB toolkit to query, migrate and model your database
We analyzed this package 23 days ago, and awarded it 60 pub points (of a possible 160):
0/10 points: Provide a valid pubspec.yaml
Failed to verify repository URL.
Repository has no matching pubspec.yaml with name: prisma_cli.
Please provide a valid repository URL in pubspec.yaml, such that:
repositorycan be cloned,- a clone of the repository contains a
pubspec.yaml, which:,- contains
name: prisma_cli, - contains a
versionproperty, and, - does not contain a
publish_toproperty.
- contains
5/5 points: Provide a valid README.md
5/5 points: Provide a valid CHANGELOG.md
10/10 points: Use an OSI-approved license
Detected license: BSD-3-Clause.
10/10 points: 20% or more of the public API has dartdoc comments
3 out of 4 API elements (75.0 %) have documentation comments.
Some symbols that are missing documentation: prisma_cli.
0/10 points: Package has an example
No example found.
See package layout guidelines on how to add an example.
20/20 points: Supports 5 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
-
✓ Android
-
✓ iOS
-
✓ Windows
-
✓ Linux
-
✓ macOS
These platforms are not supported:
Package not compatible with platform Web
Because:
package:prisma_cli/prisma_cli.dartthat imports:package:prisma_cli/src/prisma_cli.dartthat imports:package:prisma_cli/src/commands/init_command.dartthat imports:package:prisma_cli/src/utils/ansi_progress.dartthat imports:dart:io
0/50 points: code has no errors, warnings, lints, or formatting issues
Found 13 issues. Showing the first 2:
ERROR: Target of URI doesn't exist: '../dmmf/dmmf.dart'.
bin/src/commands/generate_command.dart:7:8
╷
7 │ import '../dmmf/dmmf.dart';
│ ^^^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze bin/src/commands/generate_command.dart
ERROR: Target of URI doesn't exist: '../logger.dart'.
bin/src/commands/generate_command.dart:8:8
╷
8 │ import '../logger.dart';
│ ^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze bin/src/commands/generate_command.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
archive |
^3.3.1 |
3.6.1 | 4.0.7 | |
args |
^2.3.1 |
2.7.0 | 2.7.0 | |
http |
^0.13.4 |
0.13.6 | 1.6.0 | |
json_annotation |
^4.6.0 |
4.9.0 | 4.9.0 | |
path |
any |
1.9.1 | 1.9.1 | |
yaml |
any |
3.1.3 | 3.1.3 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
async |
- | 2.13.0 | 2.13.0 | |
collection |
- | 1.19.1 | 1.19.1 | |
crypto |
- | 3.0.7 | 3.0.7 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
meta |
- | 1.17.0 | 1.17.0 | |
source_span |
- | 1.10.1 | 1.10.1 | |
string_scanner |
- | 1.4.1 | 1.4.1 | |
term_glyph |
- | 1.2.2 | 1.2.2 | |
typed_data |
- | 1.4.0 | 1.4.0 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
The constraint `^3.3.1` on archive does not support the stable version `4.0.0`.
Try running dart pub upgrade --major-versions archive to update the constraint.
The constraint `^0.13.4` on http does not support the stable version `1.0.0`.
Try running dart pub upgrade --major-versions http to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
0/20 points: Compatible with dependency constraint lower bounds
downgrade analysis failed failed with 13 errors:
URI_DOES_NOT_EXIST-bin/src/commands/generate_command.dart:7:8- Target of URI doesn't exist: '../dmmf/dmmf.dart'.URI_DOES_NOT_EXIST-bin/src/commands/generate_command.dart:8:8- Target of URI doesn't exist: '../logger.dart'.UNDEFINED_CLASS-bin/src/commands/generate_command.dart:33:11- Undefined class 'EngineOptions'.
Run dart pub downgrade and then dart analyze to reproduce the above problem.
You may run dart pub upgrade --tighten to update your dependency constraints, see dart.dev/go/downgrade-testing for details.
Analyzed with Pana 0.23.3, Dart 3.10.4.
Check the analysis log for details.