← Home

@swc/register

npm Repository Homepage

Super fast alternative for babel-register

10
Versions
(Apache-2.0 OR MIT)
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

kdy1

Keywords

swctypescriptbabel

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:dynamic-require AI (semgrep): Test-only dynamic require of local build path, not exploitable. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript used via tsc build step, not a direct import; stable FP. ai
provenance missing-githead AI (provenance): Metadata-only regression, no malicious behavior; consistent trusted publisher. ai

Versions (showing 10 of 10)

Version Deps Published
0.1.10 3 / 9
0.1.9 3 / 9
0.1.8 3 / 9
0.1.7 4 / 9
0.1.6 4 / 9
0.1.5 4 / 9
0.1.4 4 / 6
0.1.2 4 / 6
0.1.1 4 / 6
0.1.0 4 / 6

v0.1.9

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.

LOW No provenance attestation provenance

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

v0.1.8

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kdy1.

LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.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.

v0.1.2

2 findings
HIGH dynamic-require: __tests__/index.js:48 semgrep

Dynamic require() with a variable — could load arbitrary modules Source: https://github.com/swc-project/register/blob/f5d261cc21d72e35a0f89e21f83a49a9e614c8fb/__tests__/index.js#L48 46 | }; 47 | > 48 | swcRegister = require(registerFile); 49 | swcRegister.default(config); 50 | }

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.

v0.1.1

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.

v0.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.