@drax/audit-front
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Part of established @drax monorepo; sparse metadata is a style choice, not a spam indicator. | ai | |
| phantom-deps | phantom-dep:@drax/common-front | AI (phantom-deps): Same-org dependency likely re-exported via index; stable false positive for this monorepo package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.29.0 | 3 / 3 | |
| 3.20.0 | 3 / 3 | |
| 3.11.0 | 3 / 3 | |
| 2.11.0 | 3 / 3 | |
| 2.6.0 | 3 / 3 | |
| 2.0.1 | 3 / 3 | |
| 1.4.0 | 3 / 5 | |
| 1.2.2 | 3 / 5 | |
| 0.51.0 | 3 / 5 | |
| 0.49.2 | 3 / 5 | |
| 0.49.0 | 3 / 5 | |
| 0.47.0 | 3 / 5 | |
| 0.43.0 | 3 / 5 | |
| 0.39.0 | 3 / 5 | |
| 0.38.0 | 3 / 5 |
v3.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.