bigint-mod-arith
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by known-maintainer manual publish, not compromise. | ai | |
| source-diff | obfuscated-file:dist/index.node.cjs | AI (source-diff): Rollup/terser minified output with source map to src/ts; benign build artifact. | ai | |
| source-diff | obfuscated-file-transition:dist/bundles/esm.js | AI (source-diff): Rollup/terser bundle output; readable source with no malicious payload, stable for this build. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Same maintainer's alt account matched by email; not a hijack. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 0 / 28 | |
| 3.3.0 | 0 / 28 | |
| 3.2.1 | 0 / 28 | |
| 3.2.0 | 0 / 27 | |
| 3.1.2 | 0 / 26 | |
| 3.1.1 | 0 / 27 | |
| 3.1.0 | 0 / 27 | |
| 3.0.2 | 0 / 26 | |
| 3.0.1 | 0 / 25 | |
| 3.0.0 | 0 / 24 |
v3.3.0
3 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.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2023-06-28, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.1
3 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.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2023-04-13, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2023-04-11, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.2
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2022-10-03, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.1
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2022-09-12, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.0
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2022-08-01, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.2
3 findingsThis file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (juanelasisme) than the most recent previously approved version (juanelas) on 2022-01-17, but juanelasisme is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.