mrkeyoor.comAsk

jnz/INSLIBtested 01 Oct 2026commit 4d13deb

INSLIB review

Evaluate INSLIB for embedded navigation work if your team can validate sensor preparation and target behavior.

  • Install 34 s
  • Build 4 s
81/97passed, run exited non-zero
  • 63 packages
Dataevaluationupdated 01 Nov 2026
+2stars / 7d

Evaluate INSLIB if you need an embedded C11 navigation core and can validate your own sensor integration; allow time to investigate the Python setup before adopting it. INSLIB combines inertial measurements with external sensor inputs to estimate navigation state. In our run on October 1, 2026, at commit 4d13deb, installation succeeded, but the Python tests did not complete cleanly. We did not validate navigation accuracy, live sensor operation or deployment on target hardware.

Verdict

Evaluate INSLIB for embedded navigation work if your team can validate sensor preparation and target behavior. Our run on October 1, 2026, at commit 4d13deb installed in 34 seconds; the build step returned zero in 4 seconds, but pytest encountered missing firmware files and a missing native library. Resolve those reproduction problems before depending on the Python workflow. Our run did not test navigation accuracy or hardware deployment.

We ran it

Lab card: what happened when we ran INSLIB
Lab card from our sandbox run
Screenshot of INSLIB (github.com/jnz/INSLIB)
github.com/jnz/INSLIB
Install✓ · 34s63 packages · 551 MB
Build✓ · 4s
Tests✗ · 15s81 passed · 11 failed · 7 skipped · 5 errors of 97 (pytest)
Known vulns0(pip-audit)
Repo366 files~98,003 lines of source · 226.6 MB · 1 CI workflows · tests dir

Answers from our run

Does INSLIB build from source?

Dependencies installed in 34 seconds (63 packages), and the build succeeded in 4 seconds. We cloned commit 4d13deb into a clean Debian container with 3 CPUs and no project-specific setup.

Do INSLIB's tests pass?

No. The project's own test command finished in 15 seconds and reported 81 passed, 11 failed, 7 skipped, 5 collection errors (pytest).

Does INSLIB have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use INSLIB?

Teams that need evidence of a working Python replay workflow immediately after installation: our recorded suite encountered missing native-library and firmware-file errors.

What are the alternatives to INSLIB?

KF-GINS, pyins. Evaluate INSLIB for embedded navigation work if your team can validate sensor preparation and target behavior.

Setup2/5Installation and the build step succeeded, but the recorded Python suite encountered missing native-library and firmware-file problems.
Docs5/5The supplied README documents tutorials, a manual, setup, sensor formats and specific pitfalls; individual documentation paths were not all verified.
Community3/5Retained mixed historical signal rating: the existing page records 584 stars and no open issues or PRs, without independent current verification or evidence of support responsiveness.
Maturity4/5The release page identifies v1.1.1 and the current README documents verification artifacts; our Python suite failed and hardware behavior remains untested.

Who it’s for

Embedded navigation engineers who can integrate and validate a C11 filter on their target hardware.
Teams with synchronized, calibrated sensor recordings and the expertise to check coordinate frames, latency and filter settings.
Developers who want documented requirements traceability and static-analysis artifacts alongside replay tools.

Who it’s NOT for

Teams that need evidence of a working Python replay workflow immediately after installation: our recorded suite encountered missing native-library and firmware-file errors.
Buyers who require demonstrated certification or hardware qualification; our sandbox established neither.
Projects unable to accept the recorded AGPL-3.0 license.
Teams expecting all reference-board firmware and associated host tools to be public; the current README explicitly says they are not.

Setup reality

Our sandbox ran the Python project under python/ on October 1, 2026, at commit 4d13deb. Installation succeeded in 34 seconds. The build step returned exit code 0 in 4 seconds; the test step returned exit code 1 after 15 seconds. The environment contained 63 dependency packages and occupied 551 MB.

The stored parser summaries record 81 passed, 11 failed, 7 skipped, 5 errors and total=97. These fields are not a reconciled count of unique tests, and we do not add them together or describe them as exhaustive coverage. Skipped tests remain separate from failures.

The raw tail identifies nine protocol-test failures involving missing files under embedded/stm32f429, two runner-test failures involving libINSLIB, and five test-module errors involving the same native library. The current README documents recursive submodule checkout and a Python setup script that also runs make pylib. That is a useful reproduction path, not evidence that we executed that exact procedure successfully in the older run.

Should you use INSLIB?

INSLIB is worth evaluating when your requirement is an inspectable embedded navigation core and your team can test the complete sensor chain. Our October 1, 2026, sandbox run at commit 4d13deb leaves Python integration unresolved. It provides no navigation-accuracy result and no evidence of a successful live receiver, GUI replay or target-hardware deployment.

The current README describes a C11 core with no heap allocation or operating-system dependencies. It documents fusion of IMU data with GNSS, barometer, magnetometer and other aiding inputs. Those properties give an embedded team concrete reasons to investigate it, but they do not establish suitability for a particular controller or safety requirement.

What our sandbox actually recorded

Installation succeeded in 34 seconds. The build step returned exit code 0 in 4 seconds; the test step returned exit code 1 after 15 seconds. The sandbox used Python 3.12 on Debian Bookworm with 3 CPUs and 8 GB RAM. These are observations from our run, not a new execution for this correction.

Our harness records command outcomes through success flags, exit codes, elapsed time and parsed test summaries. Its stored parser summaries list 81 passed, 11 failed, 7 skipped, 5 errors and total=97. The fields do not establish exhaustive unique test coverage. We have not reconciled a complete log, and we retain the stored values rather than replacing them with a sum.

The supplied raw pytest footer reports 10.12 seconds, whereas the stored harness test duration is 15 seconds. We retain the harness duration for the step and treat the footer as pytest's own reported duration.

The MrKeyoor testing methodology explains how command outcomes and parser summaries reach our reviews. That page describes the publisher's methodology when fetched on October 31, 2026; it does not establish that every detail of that version applied to this October 1 run.

The failures identify two reproduction problems

The raw test tail reports that libINSLIB was missing from the Python package. Two runner tests failed with that error, and five modules encountered errors for the same reason: test_binding.py, test_growth_rate.py, test_heading_stream.py, test_mount_rotation.py and test_score_leverarm.py. The error instructs the user to build the library with make pylib.

Separately, nine protocol tests failed while trying to read firmware files under embedded/stm32f429. The missing paths include cfg_keys.h, ubx.h, cfg_ubx.h, imu_saturation.h and app.c. The log establishes absent files at those paths; it does not establish why they were absent.

The successful build-step exit code therefore does not prove that the native binding was available to pytest. It also does not prove a replay workload or CLI deployment worked. The retained build tail is empty, so it cannot explain what that step produced.

Reproduce the native setup before testing your data

The current README documents KFCore as a git submodule and asks users to clone recursively. Its Python quick start uses python/setup_venv.sh, which also invokes make pylib, followed by environment activation. Dataset replay uses sensor CSV files and a YAML configuration.

For evaluation, first reproduce the documented setup on the exact source revision you intend to use. Confirm that the Python binding loads, investigate the firmware-dependent test paths, and rerun the relevant suite before relying on replay results. These are proposed next steps; this correction contains no successful rerun.

The supplied historical README URL at the measured commit returned 404. Consequently, current setup instructions and capabilities are attributed to the current README rather than presented as verified documentation from commit 4d13deb. The v1.1.1 release page does identify that release with 4d13deb and September 28, 2026. Current README benchmarks labeled v1.3.0 are not results from our v1.1.1 run.

Sensor preparation remains your responsibility

The README requires a shared monotonic sensor timebase and consistent forward-right-down axes. It warns that calibration errors, unmeasured GNSS latency, an incorrect antenna lever arm and vibration aliasing can damage the estimate. That makes a representative recording from your own sensor installation a useful next evaluation step once the binding works.

The README also describes requirements traceability, MC/DC tracking and static stack analysis. These are upstream engineering artifacts, not checks our Python sandbox independently reproduced. They do not establish certification. Its reference-hardware section also says the board firmware and associated host tools are not public, so plan your integration around the public components you can actually obtain.

The recorded pip-audit result is zero advisories. Scan coverage is unknown: the supplied record does not establish scannedPackages, and its packages field is zero. This is not evidence that all 63 dependencies were scanned or that INSLIB is secure.

Choose an alternative by workflow

KF-GINS provides a C++ GNSS/INS workflow managed with CMake. Its documentation requires all initial states to be supplied in the configuration file. Consider it as a replacement candidate when that processing model fits your recordings, or as a separate comparison implementation during evaluation; we did not run it here. See the KF-GINS repository.

pyins provides basic inertial-navigation algorithms in a pure Python package. Consider it for a Python analysis workflow, or alongside embedded development for separate analysis. It does not establish a replacement for INSLIB's embedded C integration. Its distribution name is python-ins; see the pyins repository.

How to read the retained ratings

These editorial ratings use a 1-to-5 scale: 1 means substantial obstacles or very limited supporting evidence, 2 means material unresolved obstacles, 3 means mixed evidence, 4 means substantial supporting artifacts with important limits, and 5 means especially complete evidence within the stated dimension. They are not performance measurements.

Setup ease is 2 because the recorded installation and build outcomes coexist with unresolved native-library and firmware-file test problems. Documentation is 5 for the supplied manual references, tutorials, setup instructions and concrete sensor pitfalls; we did not verify every documented path. Community remains 3 as a mixed historical signal rating: the supplied existing page records 584 stars and an empty issue/PR queue, but those figures were not independently reverified and do not establish adoption or support responsiveness. Maturity is 4 for the identified release and documented verification artifacts, limited by our failed Python suite and lack of hardware validation.

Alternatives

ProjectWhat it isPick it when
KF-GINSA C++ extended-Kalman-filter GNSS/INS system managed with CMake.Evaluate it as a replacement candidate for a configured GNSS/INS processing workflow when you can provide all initial states, or as a separate comparison implementation.
pyinsA pure Python package providing basic inertial-navigation algorithms.Choose it for a Python analysis workflow, or use it as an analysis complement to embedded development; do not assume it replaces an embedded C core.

What people are saying

  1. [velocity-scout] jnz/INSLIB

Sources

  1. INSLIB README
  2. INSLIB repository
  3. INSLIB v1.1.1 release
  4. INSLIB AGPL-3.0 license

More data reviews