@finos/legend-extension-application-studio-depot-dashboard UNLICENSED 38 versions

@finos/legend-extension-application-studio-depot-dashboard

npm Repository

Legend extension for Depot

38

Versions

UNLICENSED

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

finos-adminmaootexodusneil.slinger

Keywords

legendlegend-extensionapplication-studio-depot-dashboardstorerelationaldatabasedb

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:serializr	AI (dependencies): serializr is a well-known MobX serialization library; stable dependency for this FINOS package.	ai	2026/05/29
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Type-only framework dep loaded by convention; stable false positive for this package.	ai	2026/04/30
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Monorepo peer dep pattern; react-dom declared for consumers, not directly imported in lib code.	ai	2026/04/30
phantom-deps	phantom-dep:ag-grid-react	AI (phantom-deps): Referenced in config files per analyzer note; not a direct import concern.	ai	2026/04/30
phantom-deps	phantom-dep:@finos/legend-application	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for intra-org packages.	ai	2026/04/30

Versions (showing 38 of 38)

Version	Deps	Published
0.1.69	16 / 10	2026-06-05
0.1.68	16 / 10	2026-06-04
0.1.67	16 / 10	2026-06-03
0.1.66	16 / 10	2026-06-03
0.1.65	16 / 10	2026-06-01
0.1.64	16 / 10	2026-05-26
0.1.63	16 / 10	2026-05-20
0.1.62	16 / 10	2026-05-18
0.1.61	16 / 10	2026-05-11
0.1.60	16 / 10	2026-05-11
0.1.59	16 / 10	2026-05-07
0.1.58	16 / 10	2026-05-06
0.1.57	16 / 10	2026-05-05
0.1.56	16 / 10	2026-05-01
0.1.55	16 / 10	2026-04-29
0.1.54	16 / 10	2026-04-27
0.1.51	16 / 10	2026-04-06
0.1.50	16 / 10	2026-03-31
0.1.49	16 / 10	2026-03-24
0.1.48	16 / 10	2026-03-24
0.1.47	16 / 10	2026-03-20
0.1.45	16 / 10	2026-03-17
0.1.41	16 / 10	2026-03-07
0.1.40	16 / 10	2026-03-06
0.1.37	16 / 10	2026-02-26
0.1.35	16 / 10	2026-02-23
0.1.34	16 / 10	2026-02-19
0.1.33	16 / 10	2026-02-14
0.1.28	16 / 10	2026-01-29
0.1.26	16 / 9	2026-01-23
0.1.24	16 / 9	2026-01-20
0.1.20	16 / 9	2026-01-06
0.1.16	16 / 9	2025-12-11
0.1.14	16 / 9	2025-12-11
0.1.11	16 / 9	2025-12-04
0.1.8	16 / 9	2025-12-02
0.1.2	16 / 9	2025-11-10
0.1.1	16 / 9	2025-11-05

v0.1.69

1 finding

LOW No provenance attestation provenance

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

v0.1.68

1 finding

LOW No provenance attestation provenance

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

v0.1.67

1 finding

LOW No provenance attestation provenance

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

v0.1.66

1 finding

LOW No provenance attestation provenance

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

v0.1.65

1 finding

LOW No provenance attestation provenance

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

v0.1.64

1 finding

LOW No provenance attestation provenance

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

v0.1.63

1 finding

LOW No provenance attestation provenance

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

v0.1.62

1 finding

LOW No provenance attestation provenance

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

v0.1.61

1 finding

LOW No provenance attestation provenance

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

v0.1.60

1 finding

LOW No provenance attestation provenance

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

v0.1.59

1 finding

LOW No provenance attestation provenance

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

v0.1.58

1 finding

LOW No provenance attestation provenance

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

v0.1.57

1 finding

LOW No provenance attestation provenance

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

v0.1.56

1 finding

LOW No provenance attestation provenance

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

v0.1.55

1 finding

LOW No provenance attestation provenance

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

v0.1.54

1 finding

LOW No provenance attestation provenance

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

v0.1.51

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

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

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

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

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

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

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

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

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

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

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

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

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

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

v0.1.16

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

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

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

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

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