@luxonis/depthai-pipeline-lib
```bash $ npm run dev ```
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@xyflow/react | AI (phantom-deps): Legitimate transitive dependency for React flow visualization; stable pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Build artifact with dist-only payload; no repo/keywords expected for compiled library. | ai | |
| phantom-deps | phantom-dep:@luxonis/common-fe-components | AI (phantom-deps): Same-org scoped package; likely re-exported or used indirectly; stable. | ai | |
| phantom-deps | phantom-dep:@dagrejs/dagre | AI (phantom-deps): Legitimate transitive dependency for graph layout; stable pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual publisher to GitHub Actions CI/CD is a documented legitimate pattern for the @luxonis org. | ai | |
| provenance | no-provenance | AI (provenance): GitHub Actions publisher for a private org scoped package; provenance absence is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:postcss-import | AI (phantom-deps): PostCSS plugins are loaded via config, not direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:rehype-sanitize | AI (phantom-deps): Likely used via config/runtime plugin pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss-preset-env | AI (phantom-deps): PostCSS plugins are loaded via config, not direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss-nested | AI (phantom-deps): PostCSS plugins are loaded via config, not direct imports; stable false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.2.1 | 7 / 6 | |
| 3.2.0 | 7 / 6 | |
| 3.1.0 | 7 / 6 | |
| 3.0.2 | 7 / 6 | |
| 3.0.1 | 7 / 6 | |
| 1.17.1 | 7 / 7 | |
| 1.17.0 | 7 / 7 | |
| 1.16.2 | 7 / 7 | |
| 1.16.1 | 7 / 7 | |
| 1.16.0 | 7 / 7 | |
| 1.15.0 | 7 / 7 | |
| 1.14.0 | 7 / 7 | |
| 1.13.0 | 7 / 7 | |
| 1.12.0 | 7 / 7 | |
| 1.11.0 | 7 / 22 | |
| 1.10.0 | 7 / 22 | |
| 1.9.0 | 7 / 22 | |
| 1.8.0 | 7 / 22 | |
| 1.7.0 | 7 / 22 | |
| 1.6.0 | 7 / 22 | |
| 1.5.0 | 7 / 22 | |
| 1.4.14 | 7 / 22 | |
| 1.4.13 | 7 / 22 | |
| 1.4.12 | 7 / 22 | |
| 1.4.11 | 7 / 22 | |
| 1.4.10 | 7 / 22 | |
| 1.4.9 | 7 / 22 |
v3.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-02. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.