← Home

export-files

npm Repository Homepage

node.js utility for exporting a directory of files as modules.

16
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

jonschlinkertdoowb

Keywords

exportexportsfilefilesmodulemodules

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from jonschlinkert to doowb occurred in 2015; both are well-known npm ecosystem maintainers. This is a stable, legitimate transition with no compromise indicators. ai
maintainer-change maintainer-added AI (maintainer-change): doowb is a prolific, trusted npm publisher (1481 approved packages) in the same ecosystem as jonschlinkert. Addition is benign and long-standing. ai
publish-pattern new-deps-added AI (publish-pattern): lazy-cache is a well-known utility by the same maintainer group, used widely across the jonschlinkert/doowb ecosystem. Not a suspicious dependency. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is the core functionality of export-files — it loads .js files from a directory as modules. This is intentional and expected behavior for this package. ai
source-diff source-size-tripled AI (source-diff): Size increase is due to inlining functionality previously delegated to lazy-cache (removed runtime dep). Legitimate refactor, not injected payload. ai

Versions (showing 16 of 16)

Version Deps Published
3.0.2 0 / 2
3.0.1 0 / 2
3.0.0 0 / 2
2.1.1 1 / 3
2.1.0 1 / 2
2.0.1 0 / 2
2.0.0 5 / 5
1.3.0 5 / 5
1.2.0 5 / 5
1.1.0 4 / 4
1.0.1 4 / 4
1.0.0 4 / 4
0.1.4 0 / 3
0.1.3 0 / 3
0.1.2 1 / 2
0.1.0 1 / 2

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.1.1

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: doowb → jonschlinkert (on 2016-01-29) provenance

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

v2.1.0

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2015-08-08) provenance

This version was published by a different npm account than previous versions on 2015-08-08. 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.

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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