build: add workflow to update unary function database

[gunjjoshi]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown status: na
• task: lint_package_json status: na
• task: lint_repl_help status: na
• task: lint_javascript_src status: na
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: na
• task: lint_javascript_tests status: na
• task: lint_javascript_benchmarks status: na
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: na
• task: lint_license_headers status: passed ---

Resolves None.

Description

What is the purpose of this pull request?

This pull request:

• adds a workflow to update the unary database.

Each time there is a change either in unary function database or in the package.json file of any package in math/base/special, the generate_unary_database script is run.

Related Issues

Does this pull request have any related issues?

None.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

{{TODO: add disclosure if applicable}}

---

@stdlib-js/reviewers

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	remark-html@​10.0.0
	remark-vdom@​8.0.0
	remark-lint-no-trailing-spaces@​3.0.2
	proxyquire-universal@​2.1.0
	mathjax-node-sre@​3.0.3
	process@​0.11.10
	tap-summary@​4.0.0
	parse-link-header@​1.0.1
	vdom-to-html@​2.3.1
	mathjax-node@​2.1.1
	remark-lint-no-auto-link-without-protocol@​1.0.4
	remark-lint-no-inline-padding@​1.0.5
	tap-xunit@​2.4.1
	remark-slug@​5.1.2
	to-vfile@​6.1.0
	tap-spec@​5.0.0
	virtual-dom@​2.1.1
	mkdirp@​0.5.6
	read-installed@​4.0.3
	proxyquireify@​3.2.1
	proxyquire@​2.1.3
	unist-util-visit@​2.0.3
	plato@​1.7.0
	remark-unlink@​2.1.2
	remark-lint-linebreak-style@​1.0.4
	remark-lint-no-html@​1.0.4
	rehype@​9.0.1
	remark-lint-no-paragraph-content-indent@​1.0.7
	remark-frontmatter@​1.3.3
	uglifyify@​5.0.2
	remark-cli@​7.0.1
	yaml@​1.10.2
	minimist@​0.0.5 ⏵ 1.2.8		+75	+9
	mustache@​4.2.0
See 72 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		[email protected] has a Critical CVE. CVE: GHSA-9q5w-79cv-947m Unsafe defaults in remark-html (CRITICAL) Affected versions: = 14.0.0; < 13.0.2; >= 14.0.0 < 14.0.1 Patched version: 13.0.2 From: package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: 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 [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has Obfuscated code. Confidence: 0.94 Location: Package overview From: ? → npm/[email protected] → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: 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 [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report