filestack-js
Official JavaScript library for 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used solely to read the package's own package.json for version detection — a standard self-versioning pattern, not arbitrary module loading. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Dependency change is @sentry/minimal -> @sentry/browser, a routine Sentry SDK consolidation. Both are official Sentry packages; no malicious signal. | ai | |
| dependencies | unvetted-dep:ts-node | AI (dependencies): ts-node is listed as a runtime dep but phantom-dep analysis confirms it is not directly imported — only referenced in config files. This is a stable quirk of this package across versions. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a standard Babel helper package loaded by convention; phantom-dep finding is expected for this type of framework-scoped package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): The base64 usage is a standard detection idiom (checking if a string is base64-encoded), not obfuscation or payload hiding. Stable false positive for this file upload SDK. | ai | |
| phantom-deps | phantom-dep:follow-redirects | AI (phantom-deps): follow-redirects is a well-known HTTP utility; phantom-dep status indicates it's used transitively, not a security concern. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is a well-known TypeScript tool used in build/config context; its phantom-dep status is a packaging hygiene issue, not a security risk. | ai | |
| phantom-deps | phantom-dep:abab | AI (phantom-deps): abab is a well-known base64/atob polyfill; phantom-dep status is a packaging hygiene issue, not a security risk. | ai |
Versions (showing 51 of 204)
| Version | Deps | Published |
|---|---|---|
| 4.3.8 | 15 / 68 | |
| 4.3.7 | 15 / 68 | |
| 4.3.6 | 15 / 68 | |
| 4.3.5 | 15 / 68 | |
| 4.3.4 | 15 / 68 | |
| 4.2.4 | 15 / 68 | |
| 4.1.4 | 15 / 68 | |
| 4.0.4 | 15 / 68 | |
| 4.0.3 | 15 / 68 | |
| 4.0.2 | 15 / 68 | |
| 4.0.1 | 15 / 68 | |
| 4.0.0 | 15 / 68 | |
| 3.51.5 | 15 / 68 | |
| 3.51.4 | 15 / 68 | |
| 3.50.4 | 15 / 68 | |
| 3.49.4 | 15 / 68 | |
| 3.48.4 | 15 / 68 | |
| 3.47.4 | 15 / 68 | |
| 3.46.4 | 15 / 68 | |
| 3.46.3 | 15 / 68 | |
| 3.46.2 | 15 / 68 | |
| 3.45.2 | 15 / 68 | |
| 3.44.2 | 15 / 68 | |
| 3.44.1 | 15 / 68 | |
| 3.43.1 | 15 / 68 | |
| 3.42.1 | 15 / 68 | |
| 3.42.0 | 15 / 68 | |
| 3.41.12 | 15 / 68 | |
| 3.40.12 | 15 / 68 | |
| 3.40.11 | 15 / 68 | |
| 3.40.10 | 15 / 68 | |
| 3.40.9 | 15 / 68 | |
| 3.40.8 | 15 / 68 | |
| 3.40.7 | 15 / 68 | |
| 3.40.6 | 15 / 68 | |
| 3.40.5 | 15 / 65 | |
| 3.39.5 | 15 / 56 | |
| 3.38.5 | 15 / 56 | |
| 3.37.5 | 15 / 56 | |
| 3.37.4 | 15 / 56 | |
| 3.36.4 | 15 / 56 | |
| 3.35.4 | 15 / 56 | |
| 3.34.4 | 15 / 56 | |
| 3.34.3 | 15 / 56 | |
| 3.33.3 | 15 / 56 | |
| 3.32.3 | 15 / 56 | |
| 3.32.2 | 15 / 56 | |
| 3.32.1 | 15 / 56 | |
| 3.32.0 | 15 / 56 | |
| 3.31.0 | 15 / 56 | |
| 3.30.2 | 15 / 56 |
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.50.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.44.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.42.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.41.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.40.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.39.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.36.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.34.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.33.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.