← Home

@things-factory/dashboard

npm Repository

module for dashboard management

77
Versions
MIT
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

woo_ramjyp220heartyohhorwengliang95nalshya113shortstopyoungwookwengliang95

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Long-established package with no provenance history; consistent across all 1200 versions. ai
dependencies unvetted-dep:@things-factory/board-ui AI (dependencies): Same-org monorepo sibling dependency; consistent versioning pattern across all releases. ai
dependencies unvetted-dep:@things-factory/auth-base AI (dependencies): Same-org monorepo sibling dependency; consistent versioning pattern across all releases. ai
dependencies unvetted-dep:@things-factory/setting-base AI (dependencies): Same-org monorepo sibling dependency; consistent versioning pattern across all releases. ai
dependencies unvetted-dep:@things-factory/board-service AI (dependencies): Same-org monorepo sibling dependency; consistent versioning pattern across all releases. ai

Versions (showing 77 of 77)

Version Deps Published
9.2.24 4 / 0
9.2.23 4 / 0
9.2.22 4 / 0
9.2.21 4 / 0
9.2.20 4 / 0
9.2.19 4 / 0
9.2.18 4 / 0
9.2.17 4 / 0
9.2.16 4 / 0
9.2.13 4 / 0
9.2.5 4 / 0
9.1.19 4 / 0
9.1.18 4 / 0
9.1.17 4 / 0
9.1.16 4 / 0
9.1.15 4 / 0
9.1.14 4 / 0
9.1.13 4 / 0
9.1.12 4 / 0
9.1.8 4 / 0
9.1.7 4 / 0
9.1.6 4 / 0
9.1.5 4 / 0
9.1.4 4 / 0
9.1.3 4 / 0
9.1.1 4 / 0
9.1.0 4 / 0
9.0.41 4 / 0
9.0.38 4 / 0
9.0.37 4 / 0
9.0.36 4 / 0
9.0.35 4 / 0
9.0.34 4 / 0
9.0.33 4 / 0
9.0.32 4 / 0
9.0.28 4 / 0
9.0.27 4 / 0
9.0.26 4 / 0
9.0.25 4 / 0
9.0.24 4 / 0
9.0.20 4 / 0
9.0.15 4 / 0
9.0.14 4 / 0
9.0.13 4 / 0
9.0.12 4 / 0
9.0.9 4 / 0
9.0.6 4 / 0
9.0.5 4 / 0
9.0.4 4 / 0
9.0.2 4 / 0
9.0.1 4 / 0
9.0.0 4 / 0
8.0.92 4 / 0
8.0.90 4 / 0
8.0.89 4 / 0
8.0.88 4 / 0
8.0.87 4 / 0
8.0.86 4 / 0
8.0.76 4 / 0
8.0.75 4 / 0
8.0.74 4 / 0
8.0.73 4 / 0
8.0.72 4 / 0
8.0.64 4 / 0
8.0.63 4 / 0
6.4.11 4 / 0
6.4.10 4 / 0
6.4.8 4 / 0
4.3.815 3 / 0
4.3.770 3 / 0
4.3.767 3 / 0
4.3.764 3 / 0
4.3.755 3 / 0
4.3.752 3 / 0
4.3.743 3 / 0
4.3.695 3 / 0
4.3.689 3 / 0

v9.2.24

1 finding
LOW No provenance attestation provenance

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

v9.2.23

1 finding
LOW No provenance attestation provenance

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

v9.2.22

1 finding
INFO No provenance attestation provenance

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

v9.2.21

1 finding
LOW No provenance attestation provenance

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

v9.2.20

1 finding
LOW No provenance attestation provenance

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

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

v9.2.17

1 finding
LOW No provenance attestation provenance

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

v9.2.16

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wengliang95 → nalshya113 (on 2026-03-25, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (wengliang95) on 2026-03-25, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.2.13

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wengliang95 → heartyoh (on 2026-03-19, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (wengliang95) on 2026-03-19, but heartyoh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.2.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wengliang95 → nalshya113 (on 2026-03-06, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (wengliang95) on 2026-03-06, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.19

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: horwengliang95 → heartyoh (on 2025-11-25, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (horwengliang95) on 2025-11-25, but heartyoh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.18

1 finding
LOW No provenance attestation provenance

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

v9.1.17

1 finding
LOW No provenance attestation provenance

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

v9.1.16

1 finding
LOW No provenance attestation provenance

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

v9.1.15

1 finding
LOW No provenance attestation provenance

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

v9.1.14

1 finding
LOW No provenance attestation provenance

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

v9.1.13

1 finding
LOW No provenance attestation provenance

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

v9.1.12

1 finding
LOW No provenance attestation provenance

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

v9.1.8

1 finding
LOW No provenance attestation provenance

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

v9.1.7

1 finding
LOW No provenance attestation provenance

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

v9.1.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-10-15, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-15, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-10-14, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-14, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-10-13, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-13, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-10-10, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-10-10, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.1

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-09-24, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-09-24, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v9.1.0

1 finding
LOW No provenance attestation provenance

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

v9.0.41

1 finding
LOW No provenance attestation provenance

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

v9.0.38

1 finding
LOW No provenance attestation provenance

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

v9.0.37

1 finding
LOW No provenance attestation provenance

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

v9.0.36

1 finding
LOW No provenance attestation provenance

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

v9.0.35

1 finding
LOW No provenance attestation provenance

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

v9.0.34

1 finding
LOW No provenance attestation provenance

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

v9.0.33

1 finding
LOW No provenance attestation provenance

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

v9.0.32

1 finding
LOW No provenance attestation provenance

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

v9.0.28

1 finding
LOW No provenance attestation provenance

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

v9.0.27

1 finding
LOW No provenance attestation provenance

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

v9.0.26

1 finding
LOW No provenance attestation provenance

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

v9.0.25

1 finding
LOW No provenance attestation provenance

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

v9.0.24

1 finding
LOW No provenance attestation provenance

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

v9.0.20

1 finding
LOW No provenance attestation provenance

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

v9.0.15

1 finding
LOW No provenance attestation provenance

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

v9.0.14

1 finding
LOW No provenance attestation provenance

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

v9.0.13

1 finding
LOW No provenance attestation provenance

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

v9.0.12

1 finding
LOW No provenance attestation provenance

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

v9.0.9

1 finding
LOW No provenance attestation provenance

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

v9.0.6

1 finding
LOW No provenance attestation provenance

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

v9.0.5

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.

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

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

v9.0.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.

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

v8.0.92

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2026-04-23, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2026-04-23, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v8.0.90

1 finding
LOW No provenance attestation provenance

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

v8.0.89

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.

v8.0.88

1 finding
LOW No provenance attestation provenance

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

v8.0.87

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.

v8.0.86

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wengliang95 → nalshya113 (on 2026-03-05, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (wengliang95) on 2026-03-05, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v8.0.76

1 finding
LOW No provenance attestation provenance

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

v8.0.75

1 finding
LOW No provenance attestation provenance

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

v8.0.74

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2026-01-02, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2026-01-02, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v8.0.73

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-12-23, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-12-23, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v8.0.72

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → nalshya113 (on 2025-12-19, known maintainer) provenance

This version was published by a different npm account (nalshya113) than the most recent previously approved version (heartyoh) on 2025-12-19, but nalshya113 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v8.0.64

1 finding
LOW No provenance attestation provenance

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

v8.0.63

1 finding
LOW No provenance attestation provenance

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

v6.4.11

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → heartyoh (on 2026-03-30, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (nalshya113) on 2026-03-30, but heartyoh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v6.4.10

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wengliang95 → heartyoh (on 2026-03-30, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (wengliang95) on 2026-03-30, but heartyoh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v6.4.8

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: wengliang95 → heartyoh (on 2026-03-29, known maintainer) provenance

This version was published by a different npm account (heartyoh) than the most recent previously approved version (wengliang95) on 2026-03-29, but heartyoh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.815

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: heartyoh → horwengliang95 (on 2026-04-16, known maintainer) provenance

This version was published by a different npm account (horwengliang95) than the most recent previously approved version (heartyoh) on 2026-04-16, but horwengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.770

1 finding
LOW No provenance attestation provenance

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

v4.3.767

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → wengliang95 (on 2026-01-29, known maintainer) provenance

This version was published by a different npm account (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-29, but wengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.764

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → wengliang95 (on 2026-01-28, known maintainer) provenance

This version was published by a different npm account (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-28, but wengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.755

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → wengliang95 (on 2026-01-20, known maintainer) provenance

This version was published by a different npm account (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-20, but wengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.752

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → wengliang95 (on 2026-01-15, known maintainer) provenance

This version was published by a different npm account (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-15, but wengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.743

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → wengliang95 (on 2026-01-08, known maintainer) provenance

This version was published by a different npm account (wengliang95) than the most recent previously approved version (nalshya113) on 2026-01-08, but wengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.695

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → horwengliang95 (on 2025-11-21, known maintainer) provenance

This version was published by a different npm account (horwengliang95) than the most recent previously approved version (nalshya113) on 2025-11-21, but horwengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v4.3.689

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → horwengliang95 (on 2025-11-02, known maintainer) provenance

This version was published by a different npm account (horwengliang95) than the most recent previously approved version (nalshya113) on 2025-11-02, but horwengliang95 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.