← Home

@devvit/scheduler

38
Versions
BSD-3-Clause
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

marcuswood23niedzielskidevvit-cli-botvedredditcolacadstinkgunschkrakabeksecurimancer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal Reddit/Devvit monorepo package; sparse metadata is expected for SDK sub-packages. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package; missing description is consistent across all @devvit/* packages. ai
provenance no-provenance AI (provenance): No provenance across the @devvit/* package family; consistent pattern, not a targeted omission. ai

Versions (showing 38 of 38)

Version Deps Published
0.13.10 3 / 7
0.13.9 3 / 7
0.13.8 3 / 7
0.13.7 3 / 7
0.13.6 3 / 7
0.13.5 3 / 7
0.13.4 3 / 7
0.13.3 3 / 7
0.13.2 3 / 7
0.13.0 3 / 7
0.12.24 3 / 7
0.12.23 3 / 7
0.12.22 3 / 7
0.12.21 3 / 7
0.12.20 3 / 7
0.12.19 3 / 7
0.12.18 3 / 7
0.12.17 3 / 7
0.12.16 3 / 7
0.12.15 3 / 7
0.12.14 3 / 7
0.12.13 3 / 7
0.12.12 3 / 7
0.12.11 3 / 7
0.12.10 3 / 7
0.12.9 3 / 7
0.12.8 3 / 7
0.12.7 3 / 7
0.12.6 3 / 6
0.12.5 3 / 6
0.12.4 3 / 6
0.12.3 3 / 6
0.12.2 3 / 6
0.12.1 3 / 6
0.12.0 3 / 5
0.11.19 3 / 5
0.11.18 3 / 5
0.11.17 2 / 5

v0.13.10

1 finding
INFO No provenance attestation provenance

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

v0.13.9

1 finding
INFO No provenance attestation provenance

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

v0.13.8

1 finding
INFO No provenance attestation provenance

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

v0.13.7

1 finding
INFO No provenance attestation provenance

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

v0.13.6

1 finding
INFO No provenance attestation provenance

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