@devvit/build-pack BSD-3-Clause 33 versions

@devvit/build-pack

npm Repository

33

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:tsv	AI (dependencies): [email protected] is a pinned, stable dependency used across many versions of this package; no malicious indicators.	ai	2026/05/02
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is a module-resolution helper in BuildInfoUtil.js; standard build-tool pattern.	ai	2026/05/01
bogus-package	bogus-package	AI (bogus-package): SDK sub-package; sparse README and no description are expected for internal monorepo components.	ai	2026/05/01
semgrep	semgrep:eval-usage	AI (semgrep): Eval is used for a named bundling hack in BundleModule.js; intentional build-tool pattern, stable across versions.	ai	2026/05/01
phantom-deps	phantom-dep:typescript	AI (phantom-deps): typescript is a build-time dep used via tsc invocation in scripts, not direct import.	ai	2026/05/01
phantom-deps	phantom-dep:@types/node	AI (phantom-deps): @types/node is a type-only dep; never directly imported, stable false positive.	ai	2026/05/01
phantom-deps	phantom-dep:tsv	AI (phantom-deps): tsv is a declared dependency used via config/tooling, not direct import; false positive for this package.	ai	2026/05/01

Versions (showing 33 of 33)

Version	Deps	Published
0.13.2	8 / 9	2026-06-02
0.13.0	8 / 9	2026-05-26
0.12.24	9 / 9	2026-05-18
0.12.23	9 / 9	2026-05-11
0.12.22	9 / 9	2026-05-01
0.12.21	9 / 9	2026-04-27
0.12.20	9 / 9	2026-04-20
0.12.19	9 / 9	2026-04-13
0.12.18	9 / 9	2026-04-06
0.12.17	9 / 9	2026-03-30
0.12.16	9 / 9	2026-03-23
0.12.15	9 / 9	2026-03-16
0.12.14	9 / 9	2026-03-09
0.12.13	9 / 9	2026-02-17
0.12.12	9 / 9	2026-02-09
0.12.11	9 / 9	2026-02-02
0.12.10	9 / 9	2026-01-26
0.12.9	9 / 9	2026-01-20
0.12.8	9 / 9	2026-01-12
0.12.7	9 / 9	2025-12-22
0.12.6	8 / 9	2025-12-15
0.12.5	8 / 9	2025-12-02
0.12.4	8 / 9	2025-11-24
0.12.3	8 / 9	2025-11-17
0.12.2	8 / 9	2025-11-12
0.12.1	7 / 9	2025-10-13
0.12.0	7 / 9	2025-08-13
0.11.19	6 / 9	2025-07-23
0.11.18	6 / 7	2025-07-01
0.11.17	6 / 7	2025-06-16
0.11.16	6 / 6	2025-05-27
0.11.15	7 / 6	2025-05-08
0.11.14	7 / 7	2025-05-06

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.12.19

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.6

1 finding

LOW No provenance attestation provenance

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

v0.12.5

1 finding

LOW No provenance attestation provenance

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

v0.12.4

1 finding

LOW No provenance attestation provenance

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

v0.12.3

1 finding

LOW No provenance attestation provenance

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

v0.12.2

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

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.19

1 finding

LOW No provenance attestation provenance

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

v0.11.18

1 finding

LOW No provenance attestation provenance

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

v0.11.17

1 finding

LOW No provenance attestation provenance

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

v0.11.16

1 finding

LOW No provenance attestation provenance

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

v0.11.15

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

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.