@roomstay/ui
UI things shared between Roomstay libraries
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Webpack production bundle of a UI lib, not true obfuscation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped @roomstay/ui package; not a plausible typosquat of pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @roomstay/ui package; not a plausible typosquat of qs. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped @roomstay/ui package; not a plausible typosquat of uuid. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @roomstay/ui package; not a plausible typosquat of yup. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a declared runtime dependency; phantom-dep is a false positive for this build-output package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @roomstay/ui package; not a plausible typosquat of joi. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.15 | 1 / 29 | |
| 0.0.14 | 1 / 29 | |
| 0.0.13 | 1 / 29 | |
| 0.0.12 | 1 / 29 | |
| 0.0.11 | 1 / 29 | |
| 0.0.10 | 1 / 31 | |
| 0.0.9 | 1 / 31 | |
| 0.0.8 | 1 / 31 | |
| 0.0.7 | 0 / 12 | |
| 0.0.6 | 0 / 12 | |
| 0.0.2 | 0 / 9 | |
| 0.0.1 | 0 / 9 |
v0.0.12
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.
v0.0.11
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.
v0.0.10
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.
v0.0.9
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.
v0.0.8
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.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.