@drumee/ui-core AGPL-3.0-or-later 29 versions

@drumee/ui-core

npm Repository Homepage

Drumee Rendering Engine Core Library

29

Versions

AGPL-3.0-or-later

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

somanostrieuvy202

Keywords

JavascriptUserInterfacePatternDesignMVCClient-sideRenderingEngineJson-based

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:backbone.radio	AI (phantom-deps): backbone.radio is used via Backbone.Radio namespace, not a direct import; stable false positive.	ai	2026/05/29
semgrep	semgrep:dynamic-require	AI (semgrep): Sample shows a static string require('./utils'), not a truly dynamic variable-based require.	ai	2026/05/29
phantom-deps	phantom-dep:d3pie	AI (phantom-deps): d3pie declared as dependency; referenced in config, consistent with chart plugin usage.	ai	2026/05/25
phantom-deps	phantom-dep:d3-selection	AI (phantom-deps): d3-selection declared as dependency; referenced in config, consistent with d3 ecosystem usage.	ai	2026/05/25
phantom-deps	phantom-dep:d3	AI (phantom-deps): d3 is declared as a dependency and referenced in config; phantom-dep heuristic fires due to indirect/lazy usage.	ai	2026/05/25
phantom-deps	phantom-dep:@drumee/ui-styles	AI (phantom-deps): Same-org package declared as dependency; phantom-dep heuristic is a false positive for style-only deps.	ai	2026/05/25
phantom-deps	phantom-dep:gsap	AI (phantom-deps): gsap declared as dependency; referenced in config files, consistent with optional animation usage.	ai	2026/05/25
semgrep	semgrep:eval-usage	AI (semgrep): eval() is used to execute embedded <exec> script tags in a UI rendering engine template parser — intentional design pattern for this package.	ai	2026/05/20

Versions (showing 29 of 29)

Version	Deps	Published
1.1.43	9 / 0	2026-05-20
1.1.42	9 / 0	2026-05-19
1.1.41	9 / 0	2026-05-14
1.1.40	11 / 0	2026-05-13
1.1.39	11 / 0	2026-05-04
1.1.38	11 / 0	2026-05-04
1.1.37	11 / 0	2026-05-01
1.1.36	11 / 0	2026-05-01
1.1.35	11 / 0	2026-05-01
1.1.34	11 / 0	2026-04-30
1.1.33	11 / 0	2026-04-30
1.1.32	11 / 0	2026-04-30
1.1.30	11 / 0	2026-04-30
1.1.29	11 / 0	2026-04-14
1.1.28	11 / 0	2026-04-07
1.1.26	11 / 0	2026-04-07
1.1.25	11 / 0	2026-04-07
1.1.24	11 / 0	2026-04-06
1.1.23	11 / 0	2026-03-28
1.1.21	11 / 0	2026-03-20
1.1.20	12 / 0	2026-03-20
1.1.19	12 / 0	2026-03-20
1.1.18	12 / 0	2026-03-19
1.1.12	16 / 0	2026-03-19
1.1.8	16 / 0	2026-03-19
1.1.7	16 / 0	2026-03-19
1.1.6	16 / 0	2026-03-19
1.1.0	15 / 0	2026-03-19
1.0.4	12 / 0	2025-11-19

v1.1.43

1 finding

LOW No provenance attestation provenance

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

v1.1.42

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.1.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.0.4

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.