← Home

@spinajs/fs

npm Repository Homepage

wrapper for file operations

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

Maintainers

gben-spina

Keywords

dicontainerspinajsdi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:etc-passwd-access AI (semgrep): Match is in a comment describing sandbox path-traversal check, not executable code. ai
phantom-deps phantom-dep:exiftool-vendored AI (phantom-deps): Replaces removed exiftool dep for same file-metadata functionality; likely used via dynamic import. ai
provenance no-provenance AI (provenance): Long-established package with consistent publish history; lack of provenance is a known stable condition. ai
publish-pattern rapid-publish AI (publish-pattern): spinajs monorepo publishes all packages simultaneously; rapid publish is expected behavior across 400+ versions. ai
dependencies unvetted-dep:exiftool AI (dependencies): exiftool 0.0.3 is a stable declared dependency present across prior approved versions of this package. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher has 206 approved packages with clean history; dormancy pattern is not indicative of takeover for this monorepo. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped @spinajs package; not a typosquat of 'qs'. Levenshtein match is spurious for scoped names. ai
phantom-deps phantom-dep:exiftool AI (phantom-deps): exiftool is a declared runtime dependency; phantom-dep false positive for this package. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped @spinajs package; not a typosquat of 'pg'. Levenshtein match is spurious for scoped names. ai
phantom-deps phantom-dep:lodash AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep false positive for this package. ai

Versions (showing 100 of 197)

Version Deps Published
2.0.482 13 / 5
2.0.470 10 / 4
2.0.468 10 / 4
2.0.466 10 / 4
2.0.465 10 / 4
2.0.464 10 / 4
2.0.463 10 / 4
2.0.462 10 / 4
2.0.461 10 / 4
2.0.460 10 / 4
2.0.458 10 / 4
2.0.457 10 / 4
2.0.456 10 / 4
2.0.455 10 / 4
2.0.453 10 / 4
2.0.452 10 / 4
2.0.451 10 / 4
2.0.450 10 / 4
2.0.449 10 / 4
2.0.448 10 / 4
2.0.447 10 / 4
2.0.446 10 / 4
2.0.445 10 / 4
2.0.444 10 / 4
2.0.441 10 / 4
2.0.439 10 / 4
2.0.436 10 / 4
2.0.435 10 / 4
2.0.434 10 / 4
2.0.432 10 / 4
2.0.430 10 / 4
2.0.429 10 / 4
2.0.428 10 / 4
2.0.427 10 / 4
2.0.426 10 / 4
2.0.425 10 / 4
2.0.424 10 / 4
2.0.423 10 / 4
2.0.422 10 / 4
2.0.421 10 / 4
2.0.420 10 / 4
2.0.419 10 / 4
2.0.417 10 / 4
2.0.415 10 / 4
2.0.414 10 / 4
2.0.413 10 / 4
2.0.412 10 / 4
2.0.411 10 / 4
2.0.409 10 / 4
2.0.408 10 / 4
2.0.406 10 / 4
2.0.405 10 / 4
2.0.403 10 / 4
2.0.402 10 / 4
2.0.401 10 / 4
2.0.399 10 / 4
2.0.398 10 / 4
2.0.397 10 / 4
2.0.395 10 / 4
2.0.393 10 / 4
2.0.392 10 / 4
2.0.390 10 / 4
2.0.386 10 / 4
2.0.384 10 / 4
2.0.383 10 / 4
2.0.382 10 / 4
2.0.381 10 / 4
2.0.378 10 / 4
2.0.374 10 / 4
2.0.373 10 / 4
2.0.372 10 / 4
2.0.371 10 / 4
2.0.370 10 / 4
2.0.369 10 / 4
2.0.368 10 / 4
2.0.367 10 / 4
2.0.361 9 / 4
2.0.249 9 / 4
2.0.170 5 / 3
2.0.169 5 / 3
2.0.168 5 / 3
2.0.167 5 / 3
2.0.166 5 / 3
2.0.164 5 / 3
2.0.163 5 / 3
2.0.162 5 / 3
2.0.161 5 / 3
2.0.160 5 / 3
2.0.159 5 / 3
2.0.158 5 / 3
2.0.157 5 / 3
2.0.156 5 / 3
2.0.155 5 / 3
2.0.154 5 / 3
2.0.153 5 / 3
2.0.152 5 / 3
2.0.151 5 / 3
2.0.150 5 / 3
2.0.149 5 / 3
2.0.148 5 / 3
Showing 100 of 197 Next page →

v2.0.482

3 findings
HIGH etc-passwd-access: lib/cjs/local-provider.js:489 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux (matched inside a comment — likely documentation, not executed code) Source: https://github.com/spinajs/exceptions/blob/002dc553b0ffffd72193d0121ac425a4083bc9ee/lib/cjs/local-provider.js#L489 487 | } 488 | // join normalizes `..` segments - verify the result still lives inside basePath > 489 | // so relative paths cannot escape the sandbox ( eg. ../../etc/passwd ) 490 | const joined = (0, path_1.join)(base, path); 491 | const rel = (0, path_1.relative)(base, joined);

HIGH etc-passwd-access: lib/mjs/local-provider.js:483 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux (matched inside a comment — likely documentation, not executed code) Source: https://github.com/spinajs/exceptions/blob/002dc553b0ffffd72193d0121ac425a4083bc9ee/lib/mjs/local-provider.js#L483 481 | } 482 | // join normalizes `..` segments - verify the result still lives inside basePath > 483 | // so relative paths cannot escape the sandbox ( eg. ../../etc/passwd ) 484 | const joined = join(base, path); 485 | const rel = relative(base, joined);

INFO No provenance attestation provenance

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

v2.0.249

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.

v2.0.170

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.

v2.0.169

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.

v2.0.168

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.

v2.0.167

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.

v2.0.166

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.

v2.0.164

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.

v2.0.163

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.

v2.0.162

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.

v2.0.161

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.

v2.0.160

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.

v2.0.159

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.

v2.0.158

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.

v2.0.157

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.

v2.0.156

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.

v2.0.155

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.

v2.0.154

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.

v2.0.153

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.

v2.0.152

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.

v2.0.151

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.

v2.0.150

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.

v2.0.149

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.

v2.0.148

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.