@appello/common
Common package with many useful features for web and mobile development
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): Standard tsdown minified bundle output; code is readable React/utility logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Standard tsdown minified ESM bundle; same rationale as CJS counterpart. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects switch to shipping only compiled dist, not source replacement with a stub. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Used in bundled dist output (visible in sample); phantom-dep heuristic misses bundled imports. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Used in bundled dist output (visible in sample); phantom-dep heuristic misses bundled imports. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 6.0.4 | 3 / 20 | |
| 6.0.3 | 3 / 20 | |
| 6.0.2 | 3 / 20 | |
| 6.0.1 | 3 / 20 | |
| 6.0.0 | 3 / 24 | |
| 5.0.0 | 3 / 31 | |
| 4.3.1 | 3 / 43 | |
| 4.3.0 | 3 / 43 | |
| 4.2.9 | 3 / 43 | |
| 4.2.8 | 3 / 43 | |
| 4.2.7 | 3 / 43 | |
| 4.2.3 | 3 / 43 | |
| 4.2.1 | 3 / 43 | |
| 4.2.0 | 3 / 43 | |
| 4.1.0 | 3 / 43 | |
| 4.0.1 | 3 / 43 | |
| 4.0.0 | 3 / 43 |
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v6.0.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.