@ui5/fs
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped SAP package @ui5/fs; Levenshtein match to 'qs' is a false positive with no brand/intent overlap. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped SAP package @ui5/fs; Levenshtein match to 'pg' is a false positive with no brand/intent overlap. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.6 | 8 / 19 | |
| 4.0.5 | 9 / 19 | |
| 4.0.4 | 9 / 19 | |
| 4.0.3 | 9 / 19 | |
| 4.0.2 | 9 / 19 |
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
2 findingsPackage name '@ui5/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.