← Home

purify-ts

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

gigobyte

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:site/src/assets/sellmycode.js AI (source-diff): File is an SVG React component with long path coordinate strings — not obfuscated code. Long lines are SVG path data, a known false positive for this detector. ai
phantom-deps phantom-dep:@types/json-schema AI (phantom-deps): @types/json-schema is a type-only dev dependency; phantom dep detection is a stable false positive for this package. ai

Versions (showing 4 of 4)

Version Deps Published
2.1.4 1 / 7
2.1.3 1 / 7
2.1.2 1 / 7
2.1.0 1 / 7

v2.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.3

2 findings
HIGH New obfuscated file: site/src/assets/sellmycode.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.