Rvt To Ifc
PendingStatic analysis audit pending.
Overview
No static analysis result has been recorded yet. Pattern checks will appear here once the artifact has been analyzed.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the chosen converter executable is malicious or not the one the user intended, it could run with the user's local permissions.
The skill expects the agent to invoke a local executable to perform the conversion. That is central to the purpose, but it means the local converter must be trusted.
- DDC RvtToIfc converter or Revit CLI used for conversion - subprocess.run() is used solely for invoking the conversion tool
Use an explicit, trusted converter path, avoid running from untrusted directories, and approve conversion commands before execution.
Users must determine which converter binary is safe and compatible before the agent runs it.
The skill relies on an external converter executable, while the supplied metadata has unknown source/homepage and no install spec or required binary declaration. This is a provenance gap, not evidence of malicious behavior.
RVT2IFCconverter.exe converts Revit files to IFC offline, without licenses
Install the converter only from a trusted source, document its location, and prefer a pinned version or checksum if available.
A broad batch run could generate many files or apply the wrong export settings across a project directory.
Batch conversion is an advertised feature and fits the purpose, but a mistaken folder or export setting could affect many output files at once.
- **Batch processing** - Convert thousands of files
Test on one RVT file first, confirm the input folder and output location, and keep backups for important project files.