@viamrobotics/motion-tools
Motion visualization with Viam
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@connectrpc/connect | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@connectrpc/connect-web | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mcous removal paired with CI publishing transition; expected org maintainer rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): devin-viam is a viam-labs org member; legitimate team change. | ai | |
| dependencies | unvetted-dep:koota | AI (dependencies): koota is a well-known ECS library; use in a 3D motion visualization package is expected and benign. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): filtrex is a legitimate expression parser replacing expr-eval; SLSA provenance confirms CI/CD publish integrity. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance present; strongest supply chain integrity signal. | ai | |
| provenance | publisher-changed | AI (provenance): Org migrated publishing to GitHub Actions CI/CD with SLSA provenance; expected for viam-labs org automation. | ai | |
| source-diff | obfuscated-file:dist/loaders/pcd/worker.inline.js | AI (source-diff): Auto-generated bundled worker code from build-workers.js script; minification is expected for inlined web workers. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by bundled Three.js worker and new 3D visualization features; consistent with added deps. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 149 new files consistent with major feature expansion in a 3D motion visualization library. | ai | |
| dependencies | unvetted-dep:uuid-tool | AI (dependencies): uuid-tool is a benign UUID utility; no malicious history or suspicious behavior. | ai | |
| phantom-deps | phantom-dep:earcut | AI (phantom-deps): Svelte component library; earcut may be used indirectly via three.js/threlte ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Viam Labs package with 125 versions; sparse README is cosmetic, not a risk signal. | ai | |
| phantom-deps | phantom-dep:@tanstack/svelte-query-devtools | AI (phantom-deps): Declared runtime dep; Svelte component library import patterns may not be detected by static analysis. | ai | |
| phantom-deps | phantom-dep:@neodrag/svelte | AI (phantom-deps): Declared runtime dep; Svelte component library import patterns may not be detected by static analysis. | ai | |
| phantom-deps | phantom-dep:filtrex | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic likely misses indirect import patterns in bundled Svelte output. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.33.0 | 7 / 80 | |
| 1.32.0 | 7 / 80 | |
| 1.31.0 | 10 / 77 | |
| 1.30.0 | 10 / 77 | |
| 1.29.1 | 11 / 76 | |
| 1.29.0 | 11 / 76 | |
| 1.28.1 | 11 / 75 | |
| 1.28.0 | 11 / 75 | |
| 1.27.1 | 11 / 75 | |
| 1.25.4 | 11 / 75 | |
| 1.25.3 | 11 / 75 | |
| 1.25.2 | 11 / 75 | |
| 1.25.1 | 11 / 75 | |
| 1.25.0 | 11 / 75 | |
| 1.24.0 | 11 / 75 | |
| 1.23.1 | 11 / 75 | |
| 1.23.0 | 11 / 75 | |
| 1.22.0 | 11 / 75 | |
| 1.21.0 | 11 / 75 | |
| 1.19.1 | 11 / 73 | |
| 1.19.0 | 11 / 73 | |
| 1.18.1 | 11 / 73 | |
| 1.18.0 | 11 / 73 | |
| 1.16.0 | 11 / 72 | |
| 1.15.7 | 11 / 72 | |
| 1.15.5 | 11 / 72 | |
| 1.13.0 | 11 / 71 | |
| 1.2.1 | 6 / 65 | |
| 1.2.0 | 6 / 65 | |
| 1.1.6 | 6 / 65 | |
| 1.1.5 | 6 / 65 | |
| 1.1.4 | 6 / 63 | |
| 1.1.3 | 4 / 67 | |
| 1.1.2 | 4 / 67 | |
| 1.1.1 | 4 / 67 | |
| 1.1.0 | 4 / 67 | |
| 1.0.3 | 4 / 67 | |
| 1.0.2 | 4 / 67 | |
| 0.19.2 | 2 / 65 | |
| 0.19.1 | 2 / 65 | |
| 0.19.0 | 1 / 65 | |
| 0.18.3 | 0 / 67 | |
| 0.18.2 | 0 / 66 | |
| 0.18.1 | 0 / 66 | |
| 0.18.0 | 0 / 66 | |
| 0.17.0 | 0 / 66 | |
| 0.16.4 | 0 / 66 | |
| 0.16.3 | 0 / 66 | |
| 0.16.2 | 0 / 66 | |
| 0.16.1 | 0 / 66 | |
| 0.16.0 | 0 / 66 |
v1.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.28.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.27.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.23.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.19.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.5
3 findingsThis version was published by a different npm account than previous versions on 2026-03-20. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.0
3 findingsThis version was published by a different npm account than previous versions on 2026-03-05. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-17. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.1
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.2
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.
v0.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.