@drax/settings-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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@drax/crud-vue | AI (phantom-deps): Same-org sibling dependency; phantom-dep heuristic false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@drax/common-front | AI (phantom-deps): Same-org sibling; likely re-exported via index without direct import in scanned files. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @drax org library; missing metadata is consistent with private/monorepo publishing pattern across 99 versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Same org, internal library pattern; no description is consistent across the @drax package family. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 3.50.0 | 5 / 15 | |
| 3.48.2 | 5 / 15 | |
| 3.48.1 | 5 / 15 | |
| 3.48.0 | 5 / 15 | |
| 3.47.0 | 5 / 15 | |
| 3.46.0 | 5 / 15 | |
| 3.39.0 | 5 / 15 | |
| 3.34.0 | 5 / 15 | |
| 3.31.0 | 5 / 15 | |
| 3.30.1 | 5 / 15 | |
| 3.30.0 | 5 / 15 | |
| 3.29.0 | 5 / 15 | |
| 3.27.0 | 5 / 15 | |
| 3.26.0 | 5 / 15 | |
| 3.25.1 | 5 / 15 | |
| 3.25.0 | 5 / 15 | |
| 3.24.0 | 5 / 15 | |
| 3.23.0 | 5 / 15 | |
| 3.22.1 | 5 / 15 | |
| 3.21.0 | 5 / 15 | |
| 3.20.0 | 5 / 15 | |
| 3.19.0 | 5 / 15 | |
| 3.18.1 | 5 / 15 | |
| 3.18.0 | 5 / 15 | |
| 3.17.0 | 5 / 15 | |
| 3.15.0 | 5 / 15 | |
| 3.14.0 | 5 / 15 | |
| 3.13.0 | 5 / 15 | |
| 3.11.0 | 5 / 15 | |
| 3.10.0 | 5 / 15 | |
| 3.8.0 | 5 / 15 | |
| 3.7.0 | 5 / 15 | |
| 3.4.1 | 5 / 15 | |
| 3.4.0 | 5 / 15 | |
| 3.3.0 | 5 / 15 | |
| 3.2.1 | 5 / 15 | |
| 3.2.0 | 5 / 15 | |
| 3.1.0 | 5 / 15 | |
| 3.0.0 | 5 / 15 | |
| 2.11.0 | 5 / 15 | |
| 2.8.0 | 5 / 15 | |
| 2.7.0 | 5 / 15 | |
| 2.6.0 | 5 / 15 | |
| 2.4.0 | 5 / 15 | |
| 2.3.0 | 5 / 15 | |
| 2.2.1 | 5 / 15 | |
| 2.2.0 | 5 / 15 | |
| 2.1.2 | 5 / 15 | |
| 2.1.0 | 5 / 15 | |
| 2.0.7 | 5 / 15 | |
| 2.0.6 | 5 / 15 |
v3.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.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. Consider requesting the maintainer enable provenance via CI/CD.
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.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.