← Home

@dpuse/dpuse-connector-file-store-emulator

npm Repository Homepage

[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE) <span><!-- OWASP_BADGES_START --> [![OWASP](https://img.shields.io/badge/OWASP-passed-4CAF50)](https://dpuse.github.io/dpuse-connector-file-store-emulator/dependency-check-rep

21
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

terrelljm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@dpuse/dpuse-tool-csv-parse AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via bundled dist — stable false positive for this package. ai
phantom-deps phantom-dep:@dpuse/dpuse-tool-rust-csv-core AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via bundled dist — stable false positive for this package. ai
phantom-deps phantom-dep:@dpuse/dpuse-tool-file-operators AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via bundled dist — stable false positive for this package. ai
phantom-deps phantom-dep:nanoid AI (phantom-deps): nanoid referenced in config; phantom-dep heuristic fires on config-only references — stable false positive. ai

Versions (showing 21 of 21)

Version Deps Published
0.2.497 5 / 26
0.2.496 5 / 26
0.2.495 5 / 26
0.2.493 5 / 26
0.2.492 5 / 26
0.2.491 5 / 26
0.2.490 5 / 26
0.2.489 5 / 26
0.2.488 5 / 26
0.2.485 5 / 26
0.2.480 5 / 26
0.2.478 5 / 26
0.2.476 5 / 26
0.2.474 5 / 26
0.2.472 5 / 26
0.2.471 5 / 26
0.2.470 5 / 26
0.2.463 3 / 28
0.2.462 3 / 28
0.2.461 2 / 29
0.2.460 2 / 29

v0.2.497

1 finding
LOW No provenance attestation provenance

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

v0.2.496

1 finding
LOW No provenance attestation provenance

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

v0.2.495

1 finding
LOW No provenance attestation provenance

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

v0.2.493

1 finding
LOW No provenance attestation provenance

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

v0.2.492

1 finding
LOW No provenance attestation provenance

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

v0.2.491

1 finding
LOW No provenance attestation provenance

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

v0.2.490

1 finding
LOW No provenance attestation provenance

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

v0.2.489

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

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

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

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

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

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

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

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

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

1 finding
LOW No provenance attestation provenance

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

v0.2.463

1 finding
LOW No provenance attestation provenance

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

v0.2.462

1 finding
LOW No provenance attestation provenance

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

v0.2.461

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

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.