@filestack/loader
Dependency free js async script loader for browsers maintained by @Filestack
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/module/index.js | AI (source-diff): dist/module/index.js is TypeScript compiler output (tsc ESM build). Long lines are from bundled compiled code, not obfuscation. Sample shows readable, benign script-loader logic from the official filestack org. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from individual dev account (pcholuj) to org account (filestack-dev) is consistent with Filestack consolidating publishing under their org. Both are Filestack employees/accounts. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): filestack-dev is the official Filestack org npm account with 230 approved packages and a 3340-day history. Addition is a legitimate org consolidation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of individual maintainer in favor of org account is a standard practice for company-owned packages under the @filestack scope. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 0 / 8 | |
| 1.0.8 | 0 / 8 | |
| 1.0.7 | 0 / 8 | |
| 1.0.6 | 0 / 8 | |
| 1.0.5 | 0 / 8 | |
| 1.0.4 | 0 / 8 | |
| 1.0.3 | 0 / 8 | |
| 1.0.2 | 0 / 7 | |
| 1.0.1 | 0 / 7 |
v1.0.9
2 findingsThis version was published by a different npm account than previous versions on 2021-03-25. 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.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.