chore: upgrade minimark deps

[preschian]

Context

PR Type

• Bugfix
• Feature
• Refactoring
• Chore

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@kodadot1/static@0.0.7	None	0	26.4 kB	vikiival
npm/@polkadot/api@15.6.1 🔁 npm/@polkadot/api@11.2.1	Transitive: environment, filesystem, network	+51	93.4 MB	polkadotjs
npm/@polkadot/types-codec@15.6.1 🔁 npm/@polkadot/types-codec@10.11.2, npm/@polkadot/types-codec@11.2.1	None	+9	5.24 MB	polkadotjs
npm/@types/express@5.0.0	None	+9	3.68 MB	types
npm/c8@7.13.0 🔁 npm/c8@7.14.0	Transitive: environment, shell	+59	2.04 MB	oss-bot
npm/changelogen@0.5.7 🔁 npm/changelogen@0.5.5	Transitive: filesystem, shell, unsafe	+75	6.68 MB	pi0
npm/eslint@8.40.0	filesystem Transitive: environment, eval, shell, unsafe	+96	10.9 MB	eslintbot
npm/express@4.21.2	environment, filesystem, network Transitive: eval, unsafe	+64	2.15 MB	jonchurch
npm/typescript@5.0.4 🔁 npm/typescript@5.7.3	None	0	39.2 MB	typescript-bot
npm/unbuild@1.2.1 🔁 npm/unbuild@3.3.1	Transitive: environment, filesystem, network, shell, unsafe	+133	42.8 MB	pi0
npm/vitest@0.31.0 🔁 npm/vitest@3.0.7	environment, eval Transitive: filesystem, network, shell, unsafe	+70	16.3 MB	oreanno

🚮 Removed packages: npm/@vitest/coverage-c8@0.33.0, npm/json-logic-js@2.0.5, npm/standard-version@9.5.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Obfuscated code	npm/@polkadot/util-crypto@13.4.3	Confidence: 0.91 Location: Package overview	sub-api/package.json sub-api/pnpm-lock.yaml	⚠︎

View full report↗︎

Next steps

What is obfuscated code?

Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware.

Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@polkadot/util-crypto@13.4.3

[vikiival]

@preschian minimark should be removed from nft-gallery

[preschian]

@preschian minimark should be removed from nft-gallery

noted