@drax/common-vue
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance across all 82 versions; consistent publishing pattern, not a new risk. | ai | |
| phantom-deps | phantom-dep:@drax/common-front | AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via peer/transitive resolution. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org library pattern; sparse metadata is consistent across 82 versions of this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable absence of description across all versions; internal package pattern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.29.0 | 2 / 11 | |
| 3.11.0 | 2 / 11 | |
| 2.11.0 | 2 / 11 | |
| 2.6.0 | 2 / 11 | |
| 2.0.1 | 2 / 11 | |
| 0.49.0 | 2 / 27 | |
| 0.46.0 | 2 / 27 | |
| 0.45.0 | 2 / 27 | |
| 0.44.1 | 2 / 27 | |
| 0.40.0 | 2 / 27 | |
| 0.38.0 | 2 / 27 | |
| 0.37.1 | 2 / 27 |
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.
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.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.40.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.