← Home

@classytic/streamline

npm Repository Homepage
15
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

siam923classytic-bot

Keywords

workflowtemporaldurabledurable-executionorchestrationmongodbmongoosesleepwaitresumehuman-in-the-loopbackground-jobsstate-machinecrash-recoveryretryparallelschedulingwebhookapproval-flowtypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Bot account matches org's own CI automation (release scripts added same version). ai
maintainer-change maintainer-added AI (maintainer-change): Same org transitioning to bot-driven releases, not third-party takeover. ai
publish-pattern new-deps-added AI (publish-pattern): cron-parser is a legitimate, widely-used scheduling lib matching package's stated purpose. ai

Versions (showing 15 of 15)

Version Deps Published
2.8.2 3 / 17
2.8.1 3 / 17
2.8.0 3 / 17
2.7.0 3 / 17
2.6.0 3 / 17
2.5.0 2 / 17
2.4.0 2 / 17
2.3.4 2 / 17
2.3.3 2 / 17
2.3.1 2 / 17
2.3.0 2 / 17
2.2.0 2 / 15
2.1.0 2 / 14
2.0.0 2 / 13
1.0.0 2 / 13

v2.8.2

1 finding
LOW No provenance attestation provenance

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

v2.8.1

1 finding
LOW No provenance attestation provenance

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

v2.8.0

1 finding
LOW No provenance attestation provenance

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

v2.7.0

2 findings
HIGH Publisher changed: siam923 → classytic-bot (on 2026-07-06) provenance

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

LOW No provenance attestation provenance

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

v2.3.4

1 finding
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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