← Home

readdir-scoped-modules

Like `fs.readdir` but handling `@org/module` dirs as if they were a single entry.

4
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

isaacszkat

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): isaacs → othiym23 is a known internal npm team handoff from 2014; both are core npm maintainers. ai
maintainer-change maintainer-added AI (maintainer-change): othiym23 is a long-time npm Inc. engineer; legitimate team member addition. ai
publish-pattern new-deps-added AI (publish-pattern): graceful-fs is a canonical npm-org package; expected dependency for a filesystem utility. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.0 4 / 1
1.0.2 4 / 1
1.0.1 4 / 1
1.0.0 3 / 1

v1.1.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: zkat → isaacs (on 2019-06-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-28. This could indicate a legitimate maintainer transition or an account compromise.

v1.0.2

2 findings
HIGH Publisher changed: isaacs → zkat (on 2015-09-10) provenance

This version was published by a different npm account than previous versions on 2015-09-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Publisher changed: isaacs → othiym23 (on 2014-11-19) provenance

This version was published by a different npm account than previous versions on 2014-11-19. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

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.