mcp_ingest 0.1.1
mcp_ingest: ^0.1.1 copied to clipboard
Convert any file format to standardized document structure for the MCP knowledge system.
We analyzed this package 2 days ago, and awarded it 130 pub points (of a possible 160):
10/10 points: Provide a valid pubspec.yaml
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: MIT.
10/10 points: 20% or more of the public API has dartdoc comments
906 out of 1195 API elements (75.8 %) have documentation comments.
Some symbols that are missing documentation: mcp_ingest.AsrException.AsrException.new, mcp_ingest.AsrException.message, mcp_ingest.AsrOptions.AsrOptions.new, mcp_ingest.AsrPlugin.AsrPlugin.new, mcp_ingest.AsrPluginOptions.AsrPluginOptions.new.
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:mcp_ingest/mcp_ingest.dartthat imports:package:mcp_ingest/src/output/fragment_emitter.dartthat imports:package:mcp_ingest/src/document/document_part.dartthat imports:package:mcp_fact_graph/mcp_fact_graph.dartthat imports:package:mcp_fact_graph/src/storage/graph_storage.dartthat imports:package:mcp_fact_graph/src/graph/fact_graph.dartthat imports:package:mcp_fact_graph/src/graph/fact_node.dartthat imports:package:mcp_bundle/mcp_bundle.dartthat imports:package:mcp_bundle/src/ports/flow_port.dartthat imports:package:mcp_bundle/src/models/bundle.dartthat imports:package:mcp_bundle/src/io/bundle_resources.dartthat imports:dart:io
40/50 points: code has no errors, warnings, lints, or formatting issues
INFO: Angle brackets will be interpreted as HTML.
lib/src/core/fragment_value_type.dart:7:16
╷
7 │ /// fields: Map<String, dynamic> for Fragment values.
│ ^^^^^^^^^^^^^^^^^
╵
To reproduce make sure you are using the lints_core and run dart analyze lib/src/core/fragment_value_type.dart
0/10 points: All of the package dependencies are supported in the latest version
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
archive |
^3.0.0 |
3.6.1 | 4.0.9 | |
async |
^2.11.0 |
2.13.1 | 2.13.1 | |
crypto |
^3.0.0 |
3.0.7 | 3.0.7 | |
html |
^0.15.0 |
0.15.6 | 0.15.6 | |
markdown |
^7.0.0 |
7.3.1 | 7.3.1 | |
mcp_bundle |
^0.4.0 |
0.4.0 | 0.4.0 | |
mcp_fact_graph |
^0.2.2 |
0.2.2 | 0.2.2 | |
mime |
^1.0.0 |
1.0.6 | 2.0.0 | |
path |
^1.8.0 |
1.9.1 | 1.9.1 | |
pool |
^1.5.0 |
1.5.2 | 1.5.2 | |
stream_transform |
^2.1.0 |
2.1.1 | 2.1.1 | |
uuid |
^4.0.0 |
4.5.3 | 4.5.3 | |
xml |
^6.0.0 |
6.6.1 | 7.0.1 | |
yaml |
^3.0.0 |
3.1.3 | 3.1.3 |
Transitive dependencies
| Package | Constraint | Compatible | Latest | Notes |
|---|---|---|---|---|
args |
- | 2.7.0 | 2.7.0 | |
collection |
- | 1.19.1 | 1.19.1 | |
csslib |
- | 1.0.2 | 1.0.2 | |
fixnum |
- | 1.1.1 | 1.1.1 | |
http |
- | 1.6.0 | 1.6.0 | |
http_parser |
- | 4.1.2 | 4.1.2 | |
json_annotation |
- | 4.12.0 | 4.12.0 | |
meta |
- | 1.18.2 | 1.18.2 | |
petitparser |
- | 7.0.2 | 7.0.2 | |
source_span |
- | 1.10.2 | 1.10.2 | |
stack_trace |
- | 1.12.1 | 1.12.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 | |
web |
- | 1.1.1 | 1.1.1 |
To reproduce run dart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overrides.
Found 3 issues. Showing the first 2:
The constraint `^3.0.0` 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 `^1.0.0` on mime does not support the stable version `2.0.0`.
Try running dart pub upgrade --major-versions mime to update the constraint.
10/10 points: Package supports latest stable Dart and Flutter SDKs
20/20 points: Compatible with dependency constraint lower bounds
pub downgrade does not expose any static analysis error.
Analyzed with Pana 0.23.12, Dart 3.12.0.
Check the analysis log for details.