← Home

@devvit/test

npm Repository
21
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 — the axios compromise (March 2026) relied on exactly this gap.

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 SDK testing utility in @devvit monorepo; sparse metadata is expected for this package type. ai
npm-metadata no-description AI (npm-metadata): Internal monorepo package; missing description is consistent across all @devvit/* packages. ai
typosquat typosquat.levenshtein:jest AI (typosquat): @devvit/test is a scoped SDK package in the devvit monorepo, not a typosquat of jest. ai
typosquat typosquat.levenshtein:next AI (typosquat): @devvit/test is a scoped SDK package in the devvit monorepo, not a typosquat of next. ai
typosquat typosquat.levenshtein:vitest AI (typosquat): @devvit/test is a scoped SDK package in the devvit monorepo, not a typosquat of vitest. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() used in a Proxy trap to wrap vitest test API — standard JS pattern, not obfuscation. ai

Versions (showing 21 of 21)

Version Deps Published
0.13.2 13 / 5
0.13.0 13 / 5
0.12.24 13 / 5
0.12.23 13 / 5
0.12.22 13 / 5
0.12.21 13 / 5
0.12.20 13 / 5
0.12.19 13 / 5
0.12.18 13 / 5
0.12.17 13 / 5
0.12.16 13 / 5
0.12.15 13 / 5
0.12.14 13 / 5
0.12.13 13 / 5
0.12.12 12 / 5
0.12.11 12 / 5
0.12.10 12 / 5
0.12.9 12 / 5
0.12.8 12 / 5
0.12.7 12 / 5
0.12.6 12 / 5

v0.13.2

1 finding
LOW No provenance attestation provenance

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

v0.13.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: devvit-cli-bot → colacadstink (on 2026-05-26, known maintainer) provenance

This version was published by a different npm account (colacadstink) than the most recent previously approved version (devvit-cli-bot) on 2026-05-26, but colacadstink is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.12.24

1 finding
LOW No provenance attestation provenance

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

v0.12.23

1 finding
LOW No provenance attestation provenance

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

v0.12.22

1 finding
LOW No provenance attestation provenance

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

v0.12.20

1 finding
LOW No provenance attestation provenance

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

v0.12.19

1 finding
LOW No provenance attestation provenance

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

v0.12.18

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

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

1 finding
LOW No provenance attestation provenance

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

v0.12.15

1 finding
LOW No provenance attestation provenance

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

v0.12.14

1 finding
LOW No provenance attestation provenance

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

v0.12.13

1 finding
LOW No provenance attestation provenance

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

v0.12.12

1 finding
LOW No provenance attestation provenance

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

v0.12.11

1 finding
LOW No provenance attestation provenance

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

v0.12.10

1 finding
LOW No provenance attestation provenance

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

v0.12.9

1 finding
LOW No provenance attestation provenance

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

v0.12.8

1 finding
LOW No provenance attestation provenance

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

v0.12.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.12.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.