nosql_repository 2.1.1 nosql_repository: ^2.1.1 copied to clipboard
Repository pattern oriented towards NoSQL databases. This package defines the interfaces to be used by an application to access a database, namely for CRUD and searching.
We analyzed this package 2 days ago, and awarded it 115 pub points (of a possible 140):
0/10 points: Provide a valid pubspec.yaml
Homepage URL doesn't exist.
At the time of the analysis https://gitlab.com/squarealfa/dart_framework/-/tree/main/nosql_repository
was unreachable. Make sure that the website is reachable via HEAD
requests.
Repository URL doesn't exist.
At the time of the analysis https://gitlab.com/squarealfa/dart_framework
was unreachable. Make sure that the website is reachable via HEAD
requests.
Failed to verify repository URL.
Please provide a valid repository
URL in pubspec.yaml
, such that:
repository
can be cloned,- a clone of the repository contains a
pubspec.yaml
, which:,- contains
name: nosql_repository
, - contains a
version
property, and, - does not contain a
publish_to
property.
- contains
Unable to access git repository: Failed to run remote show origin
.
5/5 points: Provide a valid README.md
0/5 points: Provide a valid CHANGELOG.md
Links in `CHANGELOG.md` should be well formed Unable to parse 1 image link.
CHANGELOG.md:13:400
╷
13 │ <p>The change from source code repository is in protest by this project's initial and main author with what he views as <a href="https://github.blog/2022-03-02-our-response-to-the-war-in-ukraine/">GitHub's extremely week response</a> to the carnage going on in Ukraine by Russia. He would have expected at a minimum for any new business in Russia and Belarus to be suspended, which was incidentally <a href="(https://about.gitlab.com/blog/2022/03/11/gitlab-actions-to-date-regarding-russian-invasion-of-ukraine/#suspending-new-business-in-russia-and-belarus)">GitLab's course of action</a>.</p>
│ ^^^^^^^^^^^
[...]
10/10 points: Use an OSI-approved license
Detected license: MPL-2.0
.
10/10 points: 20% or more of the public API has dartdoc comments
75 out of 132 API elements (56.8 %) have documentation comments.
Some symbols that are missing documentation: repository.And.left
, repository.And.right
, repository.CreatePolicy.isAuthorized
, repository.CreatePolicy.CreatePolicy.root
, repository.DbException.code
.
10/10 points: Package has an example
20/20 points: Supports 6 of 6 possible platforms (iOS, Android, Web, Windows, macOS, Linux)
- ✓ Android
- ✓ iOS
- ✓ Windows
- ✓ Linux
- ✓ macOS
- ✓ Web
50/50 points: code has no errors, warnings, lints, or formatting issues
0/10 points: All of the package dependencies are supported in the latest version
Package | Constraint | Compatible | Latest |
---|---|---|---|
squarealfa_security |
^2.0.0 |
2.2.1 | 3.4.0 |
Transitive dependencies
Package | Constraint | Compatible | Latest |
---|---|---|---|
asn1lib |
- | 1.5.3 | 1.5.3 |
async |
- | 2.11.0 | 2.11.0 |
boolean_selector |
- | 2.1.1 | 2.1.1 |
collection |
- | 1.18.0 | 1.18.0 |
convert |
- | 3.1.1 | 3.1.1 |
crypto |
- | 3.0.3 | 3.0.3 |
crypto_keys |
- | 0.3.0+1 | 0.3.0+1 |
cryptography |
- | 2.7.0 | 2.7.0 |
ffi |
- | 2.1.2 | 2.1.2 |
http |
- | 0.13.6 | 1.2.1 |
http_parser |
- | 4.0.2 | 4.0.2 |
jose |
- | 0.3.4 | 0.3.4 |
js |
- | 0.6.7 | 0.7.1 |
matcher |
- | 0.12.16+1 | 0.12.16+1 |
meta |
- | 1.15.0 | 1.15.0 |
path |
- | 1.9.0 | 1.9.0 |
pointycastle |
- | 3.9.1 | 3.9.1 |
quiver |
- | 3.2.1 | 3.2.1 |
source_span |
- | 1.10.0 | 1.10.0 |
stack_trace |
- | 1.11.1 | 1.11.1 |
stream_channel |
- | 2.1.2 | 2.1.2 |
string_scanner |
- | 1.2.0 | 1.2.0 |
term_glyph |
- | 1.2.1 | 1.2.1 |
test_api |
- | 0.7.1 | 0.7.1 |
typed_data |
- | 1.3.2 | 1.3.2 |
x509 |
- | 0.2.4+2 | 0.2.4+2 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides
.
The constraint `^2.0.0` on squarealfa_security does not support the stable version `3.0.0`.
Try running dart pub upgrade --major-versions squarealfa_security
to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
Analyzed with Pana 0.22.3
, Dart 3.3.4
.
Check the analysis log for details.