@enhavo/dashboard
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:jquery | AI (phantom-deps): jquery is a declared dependency used as a peer/type-only import in this UI package; stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared dependency used transitively in this monorepo sub-package; stable false positive. | ai | |
| phantom-deps | phantom-dep:chart.js | AI (phantom-deps): chart.js is a declared dependency used transitively in this monorepo sub-package; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse metadata is expected and not indicative of spam. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.15.13 | 3 / 0 | |
| 0.15.12 | 3 / 0 | |
| 0.15.11 | 3 / 0 | |
| 0.15.10 | 4 / 0 | |
| 0.15.9 | 4 / 0 | |
| 0.15.8 | 4 / 0 | |
| 0.15.7 | 4 / 0 | |
| 0.15.6 | 4 / 0 | |
| 0.15.5 | 4 / 0 | |
| 0.15.4 | 4 / 0 | |
| 0.15.3 | 4 / 0 | |
| 0.15.2 | 4 / 0 | |
| 0.15.1 | 4 / 0 | |
| 0.14.7 | 4 / 0 | |
| 0.14.6 | 4 / 0 | |
| 0.14.5 | 4 / 0 | |
| 0.14.3 | 4 / 0 | |
| 0.14.2 | 4 / 0 | |
| 0.13.6 | 4 / 0 | |
| 0.12.6 | 4 / 0 |
v0.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.