@postxl/utils
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/zod-excel.decoders-DDf2v4dE.d.ts | AI (source-diff): Same as above — bundled TypeScript declaration file with long re-export lines, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/index.browser.d.ts | AI (source-diff): Long-line .d.ts files are normal bundled TypeScript declarations from tsdown; not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/zod-excel.decoders-CGmBv5CD.d.ts | AI (source-diff): Same pattern — bundled .d.ts with long export lines; stable false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from personal account to GitHub Actions CI is a legitimate automation migration, consistent with repo URL and package structure. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 1 / 2 | |
| 1.3.3 | 1 / 2 | |
| 1.3.2 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 | |
| 0.1.29 | 1 / 1 | |
| 0.1.28 | 1 / 1 |
v1.3.3
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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-19. This could indicate a legitimate maintainer transition or an account compromise.
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.
v1.3.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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-02-18. This could indicate a legitimate maintainer transition or an account compromise.
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.
v1.1.0
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: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.
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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.