← Home

@quenty/httppromise

npm Repository Homepage
23
Versions
—
License
Yes
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

quenty

Keywords

RobloxNevermoreLuahttppostpromise

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Part of NevermoreEngine monorepo with 238 versions; dormancy reflects monorepo release cadence, not takeover. ai
install-scripts install-script:preinstall AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable pattern for this monorepo package. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for Roblox Lua packages. ai
phantom-deps phantom-dep:@quenty/promise AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for Roblox Lua packages. ai

Versions (showing 23 of 23)

Version Deps Published
10.18.1 2 / 0
10.18.0 2 / 0
10.15.0 2 / 0
10.13.0 2 / 0
10.12.6 2 / 0
10.12.4 2 / 0
10.12.3 2 / 0
10.12.2 2 / 0
10.12.1 2 / 0
10.12.0 2 / 0
10.11.0 2 / 0
10.10.4 2 / 0
10.10.3 2 / 0
10.10.2 2 / 0
10.10.1 2 / 0
10.10.0 2 / 0
10.9.0 2 / 0
10.8.0 2 / 0
10.7.1 2 / 0
10.7.0 2 / 0
10.6.0 2 / 0
10.5.0 2 / 0
10.4.0 2 / 0

v10.11.0

1 finding
LOW No provenance attestation provenance

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

v10.10.4

1 finding
LOW No provenance attestation provenance

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

v10.10.3

1 finding
LOW No provenance attestation provenance

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

v10.10.2

1 finding
LOW No provenance attestation provenance

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

v10.10.1

1 finding
LOW No provenance attestation provenance

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

v10.10.0

1 finding
LOW No provenance attestation provenance

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

v10.9.0

1 finding
LOW No provenance attestation provenance

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

v10.8.0

1 finding
LOW No provenance attestation provenance

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

v10.7.1

1 finding
LOW No provenance attestation provenance

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

v10.7.0

1 finding
LOW No provenance attestation provenance

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

v10.6.0

1 finding
LOW No provenance attestation provenance

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

v10.5.0

1 finding
LOW No provenance attestation provenance

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

v10.4.0

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.