fobject
A simple promise-based wrapper for file operations that treats files as objects.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 12+ years old with 5 versions and ecosystem usage; 0.0.0 reflects the author's versioning choice, not malicious intent. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): slang and slang800 are the same author (Sean Lang); repo URL and author email both reference slang800. This is an account rename/consolidation, not a hostile takeover. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from slang800 to slang reflects the same individual consolidating npm accounts; package.json author and GitHub org confirm identity continuity. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer slang is the same person as slang800 (Sean Lang); legitimate self-transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): slang800 removed as part of account consolidation to slang; same individual, no third-party takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by account rename publish is consistent with legitimate maintenance; no code changes introduced. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.0.4 | 3 / 3 | |
| 0.0.3 | 3 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 1 / 3 | |
| 0.0.0 | 1 / 3 |
v0.0.4
3 findingsAll previous maintainers (slang800) were replaced by new maintainers (slang). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2016-05-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.