@drax/dynamic-vue No license 51 versions

@drax/dynamic-vue

npm

51

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): Established @drax org scoped package; minimal metadata is a consistent style across 103 versions, not a spam signal.	ai	2026/05/31
npm-metadata	no-description	AI (npm-metadata): Consistent across all versions of this package; org-internal style, not a malicious indicator.	ai	2026/05/31
phantom-deps	phantom-dep:@drax/media-vue	AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly in Vue component library pattern.	ai	2026/05/14
phantom-deps	phantom-dep:@drax/crud-front	AI (phantom-deps): Same-org scoped dep; consistent pattern across all @drax/* packages in this library.	ai	2026/05/14
phantom-deps	phantom-dep:@drax/common-front	AI (phantom-deps): Same-org scoped dep; consistent pattern across all @drax/* packages in this library.	ai	2026/05/14

Versions (showing 51 of 63)

View all versions

Version	Deps	Published
3.50.0	4 / 15	2026-06-02
3.48.2	4 / 15	2026-05-24
3.48.1	4 / 15	2026-05-24
3.48.0	4 / 15	2026-05-24
3.47.0	4 / 15	2026-05-23
3.46.0	4 / 15	2026-05-22
3.39.0	4 / 15	2026-05-17
3.34.0	4 / 15	2026-05-14
3.31.0	4 / 15	2026-05-12
3.30.1	4 / 15	2026-05-10
3.29.0	4 / 15	2026-05-10
3.26.0	4 / 15	2026-04-26
3.25.1	4 / 15	2026-04-26
3.25.0	4 / 15	2026-04-26
3.24.0	4 / 15	2026-04-24
3.21.0	4 / 15	2026-04-22
3.20.0	4 / 15	2026-04-21
3.19.0	4 / 15	2026-04-20
3.18.1	4 / 15	2026-04-17
3.18.0	4 / 15	2026-04-16
3.17.0	4 / 15	2026-04-14
3.15.0	4 / 15	2026-04-10
3.14.0	4 / 15	2026-04-10
3.13.0	4 / 15	2026-04-07
3.11.0	4 / 15	2026-04-06
3.10.0	4 / 15	2026-04-04
3.8.0	4 / 15	2026-03-31
3.7.0	4 / 15	2026-03-31
3.4.0	4 / 15	2026-03-26
3.3.0	4 / 15	2026-03-22
3.2.1	4 / 15	2026-03-21
3.2.0	4 / 15	2026-03-21
3.1.0	4 / 15	2026-03-21
3.0.0	4 / 15	2026-03-13
2.11.0	4 / 15	2026-03-11
2.8.0	4 / 15	2026-03-08
2.6.0	4 / 15	2026-03-03
2.4.0	4 / 15	2026-02-25
2.3.0	4 / 15	2026-02-24
2.2.1	4 / 15	2026-02-24
2.2.0	4 / 15	2026-02-23
2.1.2	4 / 15	2026-02-23
2.0.3	4 / 15	2026-02-18
2.0.2	4 / 15	2026-02-18
2.0.1	4 / 15	2026-02-17
2.0.0	4 / 15	2026-02-17
1.4.1	4 / 27	2026-02-16
1.4.0	4 / 27	2026-02-16
1.0.0	4 / 27	2026-01-28
0.51.0	4 / 27	2026-01-18
0.50.0	4 / 27	2026-01-18

v3.50.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.48.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.48.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.48.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.47.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.46.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.39.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.34.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.30.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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.26.0

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.

v3.25.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

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.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.11.0

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.

v2.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

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.

v2.4.0

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.

v2.3.0

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.

v2.2.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.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

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.

v2.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

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.

v1.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

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.

v0.51.0

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.

v0.50.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.