← Home

@devvit/shared

37
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 monorepo package; sparse metadata is expected for SDK sub-packages. ai
npm-metadata no-description AI (npm-metadata): Consistent across all @devvit/* monorepo packages; not a malice indicator here. ai
provenance no-provenance AI (provenance): No provenance across the @devvit/* package family; stable false positive. ai

Versions (showing 37 of 37)

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