@drax/crud-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:deepmerge | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires but package is a source-only lib — stable FP. | ai | |
| phantom-deps | phantom-dep:@drax/common-share | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic fires as false positive for intra-org packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org-scoped library; missing public metadata is expected, not a spam/malware indicator. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 3.21.0 | 2 / 3 | |
| 3.20.0 | 2 / 3 | |
| 3.11.0 | 2 / 3 | |
| 3.0.0 | 2 / 3 | |
| 2.11.0 | 2 / 3 | |
| 2.0.0 | 2 / 3 | |
| 1.4.1 | 2 / 5 | |
| 1.0.0 | 2 / 5 | |
| 0.51.0 | 2 / 5 | |
| 0.50.0 | 2 / 5 | |
| 0.49.0 | 2 / 5 | |
| 0.47.0 | 2 / 5 | |
| 0.46.0 | 2 / 5 | |
| 0.45.0 | 2 / 5 | |
| 0.44.1 | 2 / 5 | |
| 0.43.0 | 2 / 5 | |
| 0.42.2 | 2 / 5 | |
| 0.40.0 | 2 / 5 | |
| 0.39.0 | 2 / 5 | |
| 0.38.0 | 2 / 5 | |
| 0.37.1 | 2 / 5 | |
| 0.37.0 | 2 / 5 |
v3.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.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.0.0
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.0.0
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.50.0
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.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.1
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.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.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.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.