@sidequest/dashboard
@sidequest/dashboard is the web dashboard for Sidequest, a distributed background job queue system.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:express-ejs-layouts | AI (dependencies): express-ejs-layouts is a well-established Express middleware; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package under @sidequest org; missing metadata is expected for private tooling, not a spam/malware indicator. | ai | |
| phantom-deps | phantom-dep:ejs | AI (phantom-deps): ejs is explicitly declared in dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 8 / 7 | |
| 1.14.1 | 8 / 7 | |
| 1.14.0 | 8 / 7 | |
| 1.13.7 | 8 / 7 | |
| 1.13.6 | 8 / 7 | |
| 1.13.5 | 8 / 7 | |
| 1.13.1 | 8 / 7 | |
| 1.9.0 | 8 / 7 | |
| 1.7.1 | 8 / 7 | |
| 1.7.0 | 8 / 7 | |
| 1.6.2 | 8 / 7 | |
| 1.6.0 | 8 / 7 | |
| 1.5.0 | 8 / 7 | |
| 1.4.3 | 8 / 7 | |
| 1.4.1 | 8 / 7 | |
| 1.3.0 | 8 / 7 | |
| 1.1.1 | 8 / 7 | |
| 1.1.0 | 8 / 7 | |
| 1.0.0 | 8 / 7 |
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.1
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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.