@checkstack/dashboard-frontend
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:@checkstack/notification-common | AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for internal monorepo packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions; internal monorepo package pattern. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 60 versions; internal org publishing pattern. | ai | |
| phantom-deps | phantom-dep:@checkstack/catalog-frontend | AI (phantom-deps): Same org scope; phantom-dep heuristic unreliable for monorepo re-exports. | ai | |
| dependencies | unvetted-dep:@checkstack/auth-frontend | AI (dependencies): Workspace monorepo sibling package; workspace:* deps are resolved internally, not from npm registry. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo frontend package; missing description/repo/keywords is normal for private workspace packages. | ai | |
| dependencies | unvetted-dep:@checkstack/catalog-frontend | AI (dependencies): Workspace monorepo sibling package; workspace:* deps are resolved internally, not from npm registry. | ai | |
| phantom-deps | phantom-dep:@checkstack/command-common | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic unreliable for monorepo transitive usage. | ai | |
| phantom-deps | phantom-dep:@checkstack/command-frontend | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic unreliable for monorepo transitive usage. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.8.5 | 17 / 4 | |
| 0.8.4 | 17 / 4 | |
| 0.8.3 | 17 / 4 | |
| 0.8.2 | 17 / 4 | |
| 0.8.1 | 17 / 4 | |
| 0.8.0 | 17 / 4 | |
| 0.7.8 | 21 / 4 | |
| 0.7.4 | 21 / 4 | |
| 0.7.0 | 21 / 4 | |
| 0.6.0 | 20 / 4 | |
| 0.4.4 | 17 / 4 | |
| 0.3.35 | 17 / 4 | |
| 0.3.32 | 17 / 4 | |
| 0.3.31 | 17 / 4 | |
| 0.3.28 | 17 / 4 | |
| 0.3.25 | 17 / 4 | |
| 0.3.21 | 17 / 4 | |
| 0.3.18 | 17 / 4 | |
| 0.3.12 | 17 / 4 | |
| 0.3.11 | 17 / 4 | |
| 0.3.10 | 17 / 4 | |
| 0.3.9 | 17 / 4 | |
| 0.3.8 | 17 / 4 | |
| 0.3.7 | 17 / 4 | |
| 0.3.6 | 17 / 4 | |
| 0.3.5 | 17 / 4 | |
| 0.3.4 | 17 / 4 | |
| 0.3.3 | 17 / 4 | |
| 0.3.2 | 17 / 4 | |
| 0.3.1 | 17 / 4 | |
| 0.3.0 | 17 / 4 | |
| 0.2.0 | 18 / 4 | |
| 0.1.1 | 16 / 4 | |
| 0.1.0 | 16 / 4 | |
| 0.0.4 | 16 / 4 | |
| 0.0.3 | 16 / 4 | |
| 0.0.2 | 16 / 4 |
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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: enyineer.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.