@oh-my-pi/omp-stats
Local observability dashboard for pi AI usage statistics
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with clean track record; lack of Sigstore attestation is low risk here. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/node | AI (phantom-deps): Tailwind node plugin is referenced in build config, not directly imported in source — stable false positive for this package. | ai | |
| source-diff | obfuscated-file:dist/client/index.js | AI (source-diff): Minified React/Tailwind SPA bundle; consistent with dashboard package's declared deps and purpose. | ai | |
| phantom-deps | phantom-dep:recharts | AI (phantom-deps): recharts is a declared runtime dep used in the React dashboard UI; phantom-dep heuristic fires because it's not directly imported at the entry point. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 used to decode embedded client archive for serving dashboard assets, not for executing hidden payloads. | ai |
Versions (showing 100 of 144)
| Version | Deps | Published |
|---|---|---|
| 15.5.15 | 10 / 4 | |
| 15.5.13 | 10 / 4 | |
| 15.5.12 | 10 / 4 | |
| 15.5.11 | 10 / 4 | |
| 15.5.10 | 10 / 4 | |
| 15.5.9 | 10 / 4 | |
| 15.5.8 | 10 / 4 | |
| 15.5.7 | 10 / 4 | |
| 15.5.6 | 10 / 4 | |
| 15.5.4 | 10 / 4 | |
| 15.5.3 | 10 / 4 | |
| 15.5.2 | 10 / 4 | |
| 15.5.1 | 10 / 4 | |
| 15.5.0 | 10 / 4 | |
| 15.4.3 | 10 / 4 | |
| 15.4.2 | 10 / 4 | |
| 15.4.1 | 10 / 4 | |
| 15.3.2 | 10 / 4 | |
| 15.3.1 | 10 / 4 | |
| 15.3.0 | 10 / 4 | |
| 15.2.4 | 10 / 4 | |
| 15.2.3 | 10 / 4 | |
| 15.2.2 | 10 / 4 | |
| 15.2.1 | 10 / 4 | |
| 15.1.9 | 10 / 4 | |
| 15.1.8 | 10 / 4 | |
| 15.1.7 | 10 / 4 | |
| 15.1.6 | 10 / 4 | |
| 15.1.5 | 10 / 4 | |
| 15.1.4 | 10 / 4 | |
| 15.1.3 | 10 / 4 | |
| 15.1.2 | 10 / 4 | |
| 15.1.1 | 10 / 4 | |
| 15.1.0 | 10 / 4 | |
| 15.0.2 | 10 / 4 | |
| 15.0.1 | 10 / 4 | |
| 15.0.0 | 10 / 4 | |
| 14.9.9 | 10 / 4 | |
| 14.9.8 | 10 / 4 | |
| 14.9.7 | 10 / 4 | |
| 14.9.5 | 10 / 4 | |
| 14.9.3 | 9 / 5 | |
| 14.9.2 | 9 / 5 | |
| 14.9.1 | 9 / 5 | |
| 14.9.0 | 9 / 5 | |
| 14.8.1 | 9 / 5 | |
| 14.8.0 | 9 / 5 | |
| 14.7.8 | 9 / 5 | |
| 14.7.7 | 9 / 5 | |
| 14.7.6 | 9 / 5 | |
| 14.7.5 | 9 / 5 | |
| 14.7.4 | 9 / 5 | |
| 14.7.3 | 9 / 5 | |
| 14.7.2 | 9 / 5 | |
| 14.7.1 | 9 / 5 | |
| 14.7.0 | 9 / 5 | |
| 14.6.6 | 9 / 5 | |
| 14.6.5 | 9 / 5 | |
| 14.6.4 | 9 / 5 | |
| 14.6.3 | 9 / 5 | |
| 14.6.2 | 9 / 5 | |
| 14.6.1 | 9 / 5 | |
| 14.6.0 | 9 / 5 | |
| 14.5.14 | 9 / 5 | |
| 14.5.13 | 9 / 5 | |
| 14.5.12 | 9 / 5 | |
| 14.5.11 | 9 / 5 | |
| 14.5.10 | 9 / 5 | |
| 14.5.9 | 9 / 5 | |
| 14.5.8 | 9 / 5 | |
| 14.5.7 | 9 / 5 | |
| 14.5.6 | 9 / 5 | |
| 14.5.5 | 9 / 5 | |
| 14.5.3 | 9 / 5 | |
| 14.5.2 | 9 / 5 | |
| 14.5.1 | 9 / 5 | |
| 14.5.0 | 9 / 5 | |
| 14.4.4 | 9 / 5 | |
| 14.4.3 | 9 / 5 | |
| 14.4.1 | 9 / 5 | |
| 14.4.0 | 9 / 5 | |
| 14.3.0 | 9 / 5 | |
| 14.2.1 | 9 / 5 | |
| 14.2.0 | 9 / 5 | |
| 14.1.2 | 9 / 5 | |
| 14.1.1 | 9 / 5 | |
| 14.1.0 | 9 / 5 | |
| 14.0.5 | 9 / 5 | |
| 14.0.4 | 9 / 5 | |
| 14.0.3 | 9 / 5 | |
| 14.0.2 | 9 / 5 | |
| 13.19.0 | 9 / 5 | |
| 13.18.0 | 9 / 5 | |
| 13.17.5 | 9 / 5 | |
| 13.17.1 | 9 / 5 | |
| 13.17.0 | 9 / 5 | |
| 13.16.5 | 9 / 5 | |
| 13.16.4 | 9 / 5 | |
| 13.16.1 | 9 / 5 | |
| 13.10.0 | 9 / 5 |
v15.5.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.17.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: can1357.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.17.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: can1357.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.16.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: can1357.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: can1357.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: can1357.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.