← Home

@finos/legend-extension-store-flat-data

Legend extension for Flat-data store

100
Versions
Apache-2.0
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

finos-adminmaoo

Keywords

legendlegend-extensionstoreflat-data

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established FINOS package; provenance is a best-practice enhancement, not a security blocker. ai
dependencies unvetted-dep:serializr AI (dependencies): serializr is a well-known, stable serialization library; pinned to 3.0.3 with no known advisories. ai
phantom-deps phantom-dep:serializr AI (phantom-deps): Declared dep referenced in config; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@types/react AI (phantom-deps): Framework-scoped type package; stable false positive. ai
phantom-deps phantom-dep:mobx-react-lite AI (phantom-deps): Monorepo peer-dep pattern; stable false positive. ai
phantom-deps phantom-dep:@finos/legend-art AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo. ai
phantom-deps phantom-dep:mobx AI (phantom-deps): Monorepo peer-dep pattern; mobx is a declared dep used transitively via config. ai
phantom-deps phantom-dep:@finos/legend-shared AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo. ai
phantom-deps phantom-dep:@finos/legend-storage AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo. ai
phantom-deps phantom-dep:@finos/legend-application AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo. ai
phantom-deps phantom-dep:@finos/legend-application-studio AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo. ai
phantom-deps phantom-dep:@finos/legend-graph AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo. ai
phantom-deps phantom-dep:react AI (phantom-deps): Declared as peer dep; phantom-dep false positive for this package. ai

Versions (showing 100 of 551)

Version Deps Published
0.0.455 11 / 9
0.0.454 11 / 9
0.0.453 11 / 9
0.0.452 11 / 9
0.0.451 11 / 9
0.0.450 11 / 9
0.0.449 11 / 9
0.0.448 11 / 9
0.0.447 11 / 9
0.0.446 11 / 9
0.0.445 11 / 9
0.0.444 11 / 9
0.0.443 11 / 9
0.0.442 11 / 9
0.0.441 11 / 9
0.0.440 11 / 9
0.0.439 11 / 9
0.0.438 11 / 9
0.0.437 11 / 9
0.0.436 11 / 9
0.0.435 11 / 9
0.0.434 11 / 9
0.0.433 11 / 9
0.0.432 11 / 9
0.0.431 11 / 9
0.0.430 11 / 9
0.0.429 11 / 9
0.0.428 11 / 9
0.0.427 11 / 9
0.0.426 11 / 9
0.0.425 11 / 9
0.0.424 11 / 9
0.0.423 11 / 9
0.0.422 11 / 9
0.0.421 11 / 9
0.0.420 11 / 9
0.0.419 11 / 9
0.0.418 11 / 9
0.0.417 11 / 9
0.0.416 11 / 9
0.0.415 11 / 9
0.0.414 11 / 9
0.0.413 11 / 9
0.0.412 11 / 9
0.0.411 11 / 9
0.0.410 11 / 9
0.0.409 11 / 9
0.0.408 11 / 9
0.0.407 11 / 9
0.0.406 11 / 9
0.0.405 11 / 9
0.0.404 11 / 9
0.0.403 11 / 9
0.0.402 11 / 9
0.0.401 11 / 9
0.0.400 11 / 9
0.0.399 11 / 9
0.0.398 11 / 9
0.0.397 11 / 9
0.0.396 11 / 9
0.0.395 11 / 9
0.0.394 11 / 9
0.0.393 11 / 9
0.0.392 11 / 9
0.0.391 11 / 9
0.0.390 11 / 9
0.0.389 11 / 9
0.0.388 11 / 9
0.0.387 11 / 9
0.0.386 11 / 9
0.0.385 11 / 9
0.0.384 11 / 9
0.0.383 11 / 9
0.0.382 11 / 9
0.0.381 11 / 9
0.0.380 11 / 9
0.0.379 11 / 9
0.0.378 11 / 9
0.0.377 11 / 9
0.0.376 11 / 9
0.0.375 11 / 9
0.0.374 11 / 9
0.0.373 11 / 9
0.0.372 11 / 9
0.0.371 11 / 9
0.0.370 11 / 9
0.0.369 11 / 9
0.0.368 11 / 9
0.0.367 11 / 9
0.0.366 11 / 9
0.0.365 11 / 9
0.0.364 11 / 9
0.0.363 11 / 9
0.0.362 11 / 9
0.0.361 11 / 9
0.0.360 11 / 9
0.0.359 11 / 9
0.0.358 11 / 9
0.0.357 11 / 9
0.0.356 11 / 9
Showing 100 of 551 Next page →

v0.0.378

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.377

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.376

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.375

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.374

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.373

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.372

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.371

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.370

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.369

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.368

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.367

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.366

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.365

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.364

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.363

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.362

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.361

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.360

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.359

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.358

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.357

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.356

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.