← Home

@quenty/teamutils

npm Repository Homepage

Team utility methods

36
Versions
MIT
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

RobloxNevermoreLuaTeam

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): High-volume monorepo publisher with 887 approved packages; gap likely reflects upstream release cadence, not account takeover. ai
phantom-deps phantom-dep:@quenty/rx AI (phantom-deps): Lua-based Roblox package; JS import detection doesn't apply. Same-org deps are legitimately declared. ai
phantom-deps phantom-dep:@quenty/brio AI (phantom-deps): Lua-based Roblox package; JS import detection doesn't apply. Same-org deps are legitimately declared. ai
install-scripts install-script:preinstall AI (install-scripts): npx only-allow pnpm is a standard package manager enforcement pattern; stable across all versions of this monorepo package. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Lua-based Roblox package; JS import detection doesn't apply. Same-org deps are legitimately declared. ai
phantom-deps phantom-dep:@quenty/instanceutils AI (phantom-deps): Lua-based Roblox package; JS import detection doesn't apply. Same-org deps are legitimately declared. ai
phantom-deps phantom-dep:@quenty/maid AI (phantom-deps): Lua-based Roblox package; JS import detection doesn't apply. Same-org deps are legitimately declared. ai

Versions (showing 36 of 36)

Version Deps Published
10.31.0 5 / 0
10.30.2 5 / 0
10.30.1 5 / 0
10.29.0 5 / 0
10.27.0 5 / 0
10.25.1 5 / 0
10.25.0 5 / 0
10.22.2 5 / 0
10.22.0 5 / 0
10.20.0 5 / 0
10.19.0 5 / 0
10.18.1 5 / 0
10.18.0 5 / 0
10.17.3 5 / 0
10.17.2 5 / 0
10.17.1 5 / 0
10.17.0 5 / 0
10.16.2 5 / 0
10.16.1 5 / 0
10.16.0 5 / 0
10.15.0 5 / 0
10.14.0 5 / 0
10.13.0 5 / 0
10.12.0 5 / 0
10.11.1 5 / 0
10.11.0 5 / 0
10.10.0 5 / 0
10.9.1 5 / 0
10.9.0 5 / 0
10.8.1 5 / 0
10.8.0 5 / 0
10.7.0 5 / 0
10.6.0 5 / 0
10.5.0 5 / 0
10.4.0 5 / 0
10.3.0 5 / 0

v10.17.3

1 finding
LOW No provenance attestation provenance

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

v10.17.2

1 finding
LOW No provenance attestation provenance

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

v10.17.1

1 finding
LOW No provenance attestation provenance

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

v10.17.0

1 finding
LOW No provenance attestation provenance

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

v10.16.2

1 finding
LOW No provenance attestation provenance

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

v10.16.1

1 finding
LOW No provenance attestation provenance

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

v10.16.0

1 finding
LOW No provenance attestation provenance

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

v10.15.0

1 finding
LOW No provenance attestation provenance

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

v10.14.0

1 finding
LOW No provenance attestation provenance

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

v10.13.0

1 finding
LOW No provenance attestation provenance

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

v10.12.0

1 finding
LOW No provenance attestation provenance

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

v10.11.1

1 finding
LOW No provenance attestation provenance

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

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

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

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

v10.3.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.