@drax/dashboard-front
4
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
cincarnatoafurgeri
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped org package; sparse metadata is consistent across all 28 versions, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal library pattern; no description is stable across this package's history. | ai | |
| phantom-deps | phantom-dep:@drax/common-front | AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via type-only imports in a TS library. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.29.0 | 3 / 3 | |
| 3.25.1 | 3 / 3 | |
| 3.20.0 | 3 / 3 | |
| 3.11.0 | 3 / 3 |
v3.29.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.