@saltcorn/data
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/tests/exact_views.test.js | AI (source-diff): Compiled TypeScript Jest test output; long lines are minified test bundles, not obfuscation. Stable pattern for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; not a risk for this package. | ai | |
| phantom-deps | phantom-dep:process | AI (phantom-deps): process is a browserify polyfill listed as a dep for bundling; phantom-dep FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:tough-cookie | AI (phantom-deps): tough-cookie is a transitive peer dep pinned for override; phantom-dep FP for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; thin README and no keywords are expected and stable across versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.5.7 | 56 / 28 | |
| 1.5.6 | 56 / 28 | |
| 1.5.5 | 56 / 28 | |
| 1.4.6 | 54 / 25 | |
| 1.4.5 | 54 / 25 |
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
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.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.