← Home

@thescaffold/ntx-core

19
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

isaiahiroko

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@thescaffold/jsx-blobs AI (phantom-deps): Same-org sibling dep; phantom detection is a false positive for intra-org packages. ai
semgrep semgrep:hex-decode AI (semgrep): Fires on AES-256-CBC decryption helper using standard crypto module; legitimate cryptographic utility. ai
phantom-deps phantom-dep:nats AI (phantom-deps): Optional integration dependency referenced in config; not a direct import by design. ai
phantom-deps phantom-dep:moment AI (phantom-deps): Optional integration dependency referenced in config; not a direct import by design. ai
semgrep semgrep:base64-decode AI (semgrep): Fires on a file-conversion utility (fileTOBase64/base64TOFile); no payload execution, stable pattern for this package. ai
phantom-deps phantom-dep:ioredis AI (phantom-deps): Optional integration dependency referenced in config; not a direct import by design. ai
phantom-deps phantom-dep:@fastify/multipart AI (phantom-deps): Optional integration dependency referenced in config; not a direct import by design. ai
phantom-deps phantom-dep:amqplib AI (phantom-deps): Optional integration dependency referenced in config; not a direct import by design. ai

Versions (showing 19 of 19)

Version Deps Published
0.2.48 32 / 0
0.2.46 32 / 0
0.2.45 32 / 0
0.2.43 32 / 0
0.2.39 32 / 0
0.2.38 32 / 0
0.2.37 32 / 0
0.2.35 32 / 0
0.2.34 32 / 0
0.2.33 32 / 0
0.2.32 32 / 0
0.2.31 32 / 0
0.2.30 32 / 0
0.2.21 23 / 0
0.2.20 23 / 0
0.0.10 22 / 0
0.0.7 23 / 0
0.0.6 23 / 0
0.0.0 23 / 0

v0.2.48

1 finding
LOW No provenance attestation provenance

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

v0.2.46

1 finding
LOW No provenance attestation provenance

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

v0.2.45

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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