developer-tools Static interface comparison
Task Master MCP
0.42.0 0.43.0
REVIEWPending human review
1 schema change requires review.No new authority detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
Tools7 → 7
Added0
Removed0
Schema changes1
Input schema changes1
Output schema changes0
Unclassified schema changes0
Description changes0
New write authority0
New destructive authority0
New unknown authority0
AnalysisREVIEW
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 1Modified tools
- 1Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
1 tool with recorded changes
update_subtaskModifiedWhat changed
- update_subtask — Schema change: input property added: metadata.
- update_subtask — Schema change: input property prompt changed: description "Information to add… → "Information to add….
- update_subtask — No longer required: prompt.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Existing calls stay valid in shape, but behavior when the argument is omitted may differ.
What to verify
- Validate representative existing tool calls against the new argument schema.
- Confirm the server’s behavior when the argument is omitted.
- Declared effect
- write → write
Input schema
Property Previous (0.42.0) Current (0.43.0) Change metadatanot present stringoptional - Added
promptstringrequired stringoptional - No longer required
- Description changed
6 unchanged entries
(schema root)fileidprojectRootresearchtag
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
6 tools with no recorded change
expand_taskget_taskget_tasksnext_taskparse_prdset_task_status
Evidence and provenance
- Static findings
- REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Pending human review. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
task-master/0.42.0~0.43.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 5, 2026, 12:27 AM UTC.- Distribution
npm- Previous release
task-master-ai@0.42.07 tools · published by the registry Jan 15, 2026, 10:53 PM UTCArtifact integritysha512-6k9mDv7T7U2hI1xPXjVKQMB2Ul3N+jjYKG4D9VdnYSOAhQmvt02oYWxtgjmjBWnFqOHkRxCYR+5YIopc4WayZQ==Interface fingerprintsha256:9f17e92c7bdf1fcc2b02ba7fcea2cd107120a85c3b214603ef4a9ce49689c4ecExact interface snapshot (JSON)- Current release
task-master-ai@0.43.07 tools · published by the registry Feb 4, 2026, 1:56 PM UTCArtifact integritysha512-tS9/j8rQJb6otCZ5chZVfwUXI0YpD9OovrsBAjw8WR2z0b4p4mAVOMtT6g5aGkjC69SjxpeCo5XO/g3xNj9/GA==Interface fingerprintsha256:d5d75291a4171da07032ba3590db87815810170e1d36547f3edbcfa377019336Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Requires review
1 findingupdate_subtaskREVIEWChangedShow details
input property added: metadatainput property prompt changed: description "Information to add… → "Information to add…input required: [id, projectRoot, prompt] → [id, projectRoot]
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.