@push.rocks/smartai
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_ocr/index.js | AI (source-diff): File is readable compiled TypeScript output for Mistral OCR; long lines are normal bundler output, not obfuscation. | ai | |
| dependencies | unvetted-dep:@push.rocks/smartarray | AI (dependencies): Part of the same push.rocks ecosystem; publisher has strong track record with 57 approved packages. | ai | |
| source-diff | obfuscated-file:dist_ts_openai_chatgpt_auth/index.js | AI (source-diff): Compiled TypeScript output for OpenAI ChatGPT auth subpath export; long lines are minified JS, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist_ts/smartai.auth.openai.js | AI (source-diff): Compiled TypeScript output implementing OAuth device-code flow; content is readable and matches package purpose. | ai | |
| source-diff | obfuscated-file:dist_ts/smartai.cache.js | AI (source-diff): Compiled TypeScript cache utility; long lines are bundled output, content is benign. | ai | |
| provenance | no-provenance | AI (provenance): Publisher has consistent track record; no provenance is common for this ecosystem. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 12 / 10 | |
| 4.0.2 | 12 / 10 | |
| 4.0.1 | 12 / 10 | |
| 2.2.0 | 12 / 10 | |
| 2.0.1 | 12 / 10 | |
| 2.0.0 | 12 / 7 | |
| 0.13.3 | 10 / 7 | |
| 0.13.2 | 10 / 7 | |
| 0.13.1 | 10 / 7 | |
| 0.13.0 | 10 / 7 | |
| 0.12.1 | 10 / 7 | |
| 0.12.0 | 10 / 7 | |
| 0.11.0 | 10 / 7 | |
| 0.10.1 | 10 / 7 | |
| 0.10.0 | 10 / 7 | |
| 0.9.0 | 9 / 7 |
v4.1.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
5 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.