@gingkoo/pandora-metabase ISC 40 versions

@gingkoo/pandora-metabase

npm

## 功能概述

40

Versions

ISC

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

lizhiyong.lzybo3219188xilin.gao

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:mobx	AI (phantom-deps): mobx is a declared runtime dependency used via config/peer patterns; phantom-dep is a stable false positive for this package.	ai	2026/05/18
phantom-deps	phantom-dep:diff2html	AI (phantom-deps): UI component library; deps may be used indirectly or re-exported. Stable false positive for this package.	ai	2026/05/08
phantom-deps	phantom-dep:@types/diff	AI (phantom-deps): Type-only package loaded by TypeScript convention; not directly imported in source.	ai	2026/05/08
phantom-deps	phantom-dep:mobx-react	AI (phantom-deps): Component library; mobx-react is a runtime dep that may be used indirectly via re-exports or config.	ai	2026/05/08
phantom-deps	phantom-dep:react-scroll	AI (phantom-deps): Same pattern — declared runtime dep used via config/re-export in this component library.	ai	2026/05/08
phantom-deps	phantom-dep:@gingkoo/pandora-hooks	AI (phantom-deps): Same-org scoped dep; likely re-exported or used indirectly, stable false positive for this package.	ai	2026/05/08

Versions (showing 40 of 40)

Version	Deps	Published
1.0.116	13 / 51	2026-04-27
1.0.115	13 / 51	2026-04-17
1.0.114	13 / 51	2026-04-17
1.0.113	13 / 51	2026-04-15
1.0.112	13 / 51	2026-04-13
1.0.111	13 / 51	2026-04-07
1.0.109	13 / 51	2026-04-03
1.0.108	13 / 51	2026-03-31
1.0.107	13 / 51	2026-03-30
1.0.105	13 / 51	2026-03-27
1.0.104	13 / 51	2026-03-24
1.0.100	13 / 51	2026-03-18
1.0.98	13 / 51	2026-03-17
1.0.97	13 / 51	2026-03-17
1.0.94	13 / 51	2026-03-17
1.0.93	13 / 51	2026-03-17
1.0.92	13 / 51	2026-03-17
1.0.90	13 / 51	2026-03-13
1.0.88	13 / 51	2026-03-06
1.0.87	13 / 51	2026-03-05
1.0.86	13 / 51	2026-03-05
1.0.85	13 / 51	2026-03-05
1.0.82	13 / 51	2026-02-06
1.0.81	13 / 51	2026-02-06
1.0.79	13 / 51	2026-02-04
1.0.77	13 / 51	2026-02-04
1.0.76	13 / 51	2026-02-03
1.0.75	13 / 51	2026-02-03
1.0.72	13 / 51	2026-01-29
1.0.71	13 / 51	2026-01-20
1.0.70	13 / 51	2026-01-19
1.0.69	10 / 51	2026-01-15
1.0.68	10 / 51	2026-01-14
1.0.67	10 / 51	2026-01-07
1.0.66	10 / 51	2026-01-05
1.0.63	10 / 51	2025-11-24
1.0.62	10 / 51	2025-11-24
1.0.61	10 / 51	2025-10-31
1.0.30	10 / 51	2025-08-12
1.0.1	10 / 34	2025-07-15

v1.0.116

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v1.0.86

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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