← Home

brfs

npm Repository Homepage

browserify fs.readFileSync() static asset inliner

33
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

ahdinosauranandthakkerashaffer88baluptonbpostlethwaitebretcwmmadominictarrelnounchemilbayesferossforbeslindesayfpereira1garanngkatsevgoto-bus-stophughskindutnyjmmjprichardsonjryansleichtgewichtmafintoshmattdeslmaxogdenmellowmelonparshappkruminssethvincentstevemaosubstacktehshriketerinjokesthlorenzungoldmanyerkopalmayoshuawuytszertosh

Keywords

browserifybrowserify-transformfsreadFileSyncpluginstaticassetbundlebase64

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): goto-bus-stop is a known browserify ecosystem maintainer; publisher change reflects legitimate org-level maintainer transition. ai
maintainer-change maintainer-added AI (maintainer-change): Large maintainer list reflects browserify org's shared maintainer model with well-known Node.js contributors. ai
provenance no-provenance AI (provenance): Published in 2018, before Sigstore provenance existed. Expected for this era of packages. ai

Versions (showing 33 of 33)

Version Deps Published
2.0.2 4 / 4
2.0.1 4 / 4
2.0.0 4 / 4
1.6.1 4 / 4
1.6.0 4 / 4
1.5.0 4 / 4
1.4.4 4 / 4
1.4.3 4 / 4
1.4.2 4 / 4
1.4.1 4 / 4
1.4.0 4 / 4
1.3.0 3 / 4
1.2.0 3 / 4
1.1.2 3 / 4
1.1.1 3 / 4
1.1.0 3 / 4
1.0.2 3 / 3
1.0.1 3 / 3
1.0.0 3 / 3
0.2.2 3 / 3
0.2.1 3 / 3
0.2.0 3 / 3
0.1.0 3 / 3
0.0.9 3 / 3
0.0.8 3 / 3
0.0.7 3 / 3
0.0.6 3 / 3
0.0.5 3 / 2
0.0.4 3 / 2
0.0.3 3 / 2
0.0.2 3 / 2
0.0.1 3 / 2
0.0.0 3 / 2

v2.0.2

1 finding
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.

v1.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

v1.4.4

2 findings
HIGH Publisher changed: mattdesl → goto-bus-stop (on 2018-01-30) provenance

This version was published by a different npm account than previous versions on 2018-01-30. 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.4.3

2 findings
HIGH Publisher changed: substack → mattdesl (on 2016-01-18) provenance

This version was published by a different npm account than previous versions on 2016-01-18. 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.4.2

1 finding
LOW No provenance attestation provenance

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

v1.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.2

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.