@push.rocks/smartarchive
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_ts_shared/classes.tartools.js | AI (source-diff): Readable compiled TS output for TAR utilities; long lines from bundled data, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts_shared/bzip2/index.js | AI (source-diff): Readable bzip2 streaming decompression implementation; long lines from data arrays, not obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): tar-stream is a well-established npm package consistent with this archive library's purpose. | ai | |
| source-diff | obfuscated-file:dist_ts_shared/bzip2/bzip2.js | AI (source-diff): Long lines are CRC32 lookup table data in compiled JS, not obfuscation. Legitimate bzip2 implementation. | ai | |
| source-diff | obfuscated-file:dist_ts_shared/classes.ziptools.js | AI (source-diff): Readable compiled TS output for ZIP utilities; long lines from bundled data, not obfuscation. | ai | |
| phantom-deps | phantom-dep:through | AI (phantom-deps): through is a declared runtime dep used transitively; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/tar-stream | AI (phantom-deps): @types/tar-stream is a type-only package; phantom-dep false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.2.2 | 13 / 5 | |
| 5.2.1 | 13 / 4 | |
| 5.2.0 | 13 / 4 | |
| 5.1.0 | 12 / 3 | |
| 5.0.1 | 13 / 3 | |
| 5.0.0 | 13 / 3 | |
| 4.2.4 | 13 / 3 | |
| 4.2.3 | 14 / 3 |
v5.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
5 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.
Newly 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.
v5.2.0
5 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.
Newly 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.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
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.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.