neo2-flightpath@0.1.1
Render flight-path map overlay videos (exactly the source frame rate and frame count) from DJI drone recordings - telemetry from the .SRT sidecar or the embedded CAM-meta (DVTM) stream.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe launcher runs an ordinary CLI for processing user-supplied recordings; process execution is limited to ffmpeg/ffprobe, while network access retrieves map tiles for rendering. The `prepare` script runs the package build, and the inspected source shows no malicious collection or unrelated automatic action.
Decision evidence
public snapshot- The only lifecycle script is `prepare`, which runs the TypeScript build.
- The executable calls the CLI when the user runs the command.
- `ffmpeg` and `ffprobe` are invoked for video probing and encoding.
- Missing map tiles are fetched from the configured map providers and cached for rendering.
- Tile fetching is called as part of processing a requested recording.
- The reviewed runtime code contains no behavior that sends credentials, environment data, or project files to a collector.
- Network requests retrieve map tiles from the providers named for the rendering feature.
Source & flagged code
4 flaggedPackage source invokes a package manager install command at runtime.
dist/render.jsView on unpkg · L101Findings
Affected versions and remediation
This report applies to neo2-flightpath@0.1.1.
See all versions of neo2-flightpath for other recorded verdicts.
- Review the evidence and your use of neo2-flightpath@0.1.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.