← Home

@quenty/overriddenproperty

npm Repository Homepage

Sets properties on the client and then replicates them to the server

19
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

RobloxNevermoreLuaNetwork

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Long-standing monorepo package with unchanged content; publisher has extensive trusted history. ai
install-scripts install-script:preinstall AI (install-scripts): only-allow pnpm is a standard monorepo package-manager guard; stable across all quenty/NevermoreEngine packages. ai
phantom-deps phantom-dep:@quenty/loader AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-targeted npm packages. ai
phantom-deps phantom-dep:@quenty/throttle AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-targeted npm packages. ai
phantom-deps phantom-dep:@quenty/baseobject AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua-targeted npm packages. ai

Versions (showing 19 of 19)

Version Deps Published
10.15.0 3 / 0
10.14.2 3 / 0
10.14.1 3 / 0
10.14.0 3 / 0
10.10.2 3 / 0
10.10.1 3 / 0
10.10.0 3 / 0
10.9.3 3 / 0
10.9.2 3 / 0
10.9.1 3 / 0
10.9.0 3 / 0
10.8.2 3 / 0
10.8.1 3 / 0
10.8.0 3 / 0
10.7.0 3 / 0
10.6.0 3 / 0
10.5.0 3 / 0
10.4.0 3 / 0
10.3.0 3 / 0

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

1 finding
LOW No provenance attestation provenance

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

v10.9.2

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

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

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.