@quenty/adorneedata
Bridges attributes and serialization
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua monorepo; deps declared for tooling, not JS imports. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/rxsignal | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quentystudios/t | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/attributeutils | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/defaultvalueutils | AI (phantom-deps): Same monorepo pattern; stable false positive. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 7.33.2 | 9 / 0 | |
| 7.19.1 | 8 / 0 | |
| 7.19.0 | 8 / 0 | |
| 7.18.3 | 8 / 0 | |
| 7.18.2 | 8 / 0 | |
| 7.18.1 | 8 / 0 | |
| 7.18.0 | 8 / 0 | |
| 7.17.2 | 8 / 0 | |
| 7.17.1 | 8 / 0 | |
| 7.17.0 | 8 / 0 | |
| 7.16.0 | 8 / 0 | |
| 7.15.0 | 8 / 0 | |
| 7.14.0 | 8 / 0 | |
| 7.13.0 | 8 / 0 | |
| 7.12.2 | 8 / 0 | |
| 7.12.1 | 8 / 0 | |
| 7.12.0 | 8 / 0 | |
| 7.11.0 | 8 / 0 | |
| 7.10.1 | 8 / 0 | |
| 7.10.0 | 8 / 0 | |
| 7.9.1 | 8 / 0 | |
| 7.9.0 | 8 / 0 | |
| 7.8.0 | 8 / 0 | |
| 7.7.0 | 8 / 0 | |
| 7.6.0 | 8 / 0 | |
| 7.5.0 | 8 / 0 | |
| 7.4.0 | 8 / 0 | |
| 7.3.0 | 8 / 0 |
v7.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.