@arcanewizards/timecode-toolbox

<h1 align="center"> Timecode Toolbox </h1>

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

s0

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:osc-js	AI (phantom-deps): Monorepo package; deps declared at package level but consumed indirectly via workspace tooling.	ai	2026/04/28
phantom-deps	phantom-dep:radix-ui	AI (phantom-deps): Same monorepo pattern; indirect consumption expected.	ai	2026/04/28
phantom-deps	phantom-dep:music-metadata	AI (phantom-deps): Same monorepo pattern; indirect consumption expected.	ai	2026/04/28
phantom-deps	phantom-dep:@tailwindcss/cli	AI (phantom-deps): Used via build:styles script invocation, not direct import; expected pattern.	ai	2026/04/28
phantom-deps	phantom-dep:pino-pretty	AI (phantom-deps): pino-pretty is explicitly declared in dependencies; phantom-dep is a false positive for this package.	ai	2026/04/28

Versions (showing 6 of 6)

Version	Deps	Published
0.2.1	5 / 29	2026-05-23
0.2.0	5 / 29	2026-05-22
0.1.7	5 / 29	2026-05-16
0.1.6	5 / 29	2026-04-25
0.1.0	5 / 28	2026-04-08
0.0.3	4 / 29	2026-04-08

v0.2.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.2.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.7

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.6

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.1.0

6 findings

HIGH Publisher changed: s0 → GitHub Actions (on 2026-04-08) provenance

This version was published by a different npm account than previous versions on 2026-04-08. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New file with network + code execution: dist/index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/start.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/index.mjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: dist/start.mjs source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.3

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.