This document explains which versions of @bootgs/utils receive security fixes and how to report a vulnerability. We appreciate the work of security researchers who help keep the library and its users safe.
| Version | Package | Supported |
|---|---|---|
3.x |
@bootgs/utils |
✅ once 3.0.0 is released |
2.x |
apps-script-utils |
3.0.0 ships |
< 2.0 |
apps-script-utils |
❌ |
Version 3 is published under the new name @bootgs/utils; the 2.x line was published as apps-script-utils.
The latest release receives all fixes. Please upgrade to the latest release to stay protected; see
SUPPORT.md for the support policy.
Please do not report security vulnerabilities through public issues, discussions or pull requests.
- Preferred: use GitHub private vulnerability reporting — open the repository's Security tab → Report a vulnerability.
- Alternative: email security@maksymstoianov.com.
Please include:
- a short description and the type of issue (for example injection, prototype pollution, information disclosure);
- the affected versions;
- steps to reproduce or a proof of concept;
- the impact as you understand it, and any suggested fix.
| Step | Target |
|---|---|
| Acknowledgement of the report | within 5 business days |
| Initial assessment (validity and severity) | within 14 days |
| Fix released for critical or high severity | within 30 days of assessment |
| Fix for medium or low severity | in a regular release |
We keep you informed of progress and may ask for more details. Severity is rated with CVSS v3.1.
- We follow coordinated vulnerability disclosure: please keep the details private until a fix is released or 90 days have passed since your report, whichever comes first, unless we agree on another date together.
- Fixes are published as a new release, and confirmed vulnerabilities get a GitHub Security Advisory and, where applicable, a CVE.
- If a report is out of scope or not a vulnerability, we tell you why.
With your permission, we credit reporters by name or handle in the security advisory and release notes. Tell us in your report how you would like to be credited, or if you prefer to stay anonymous. We do not run a paid bug bounty programme.
In scope: the source code in this repository, the @bootgs/utils package published on npm and the 2.x releases
of apps-script-utils while they are supported.
Out of scope: vulnerabilities in Google Apps Script itself or other Google services (report them to Google), in development dependencies or other third-party packages (report them upstream; we will update the dependency), and in scripts built with the library that are caused by their own code or configuration.
npm package. After installing, check the registry signatures (and provenance attestations, where present) of your dependency tree:
npm audit signaturesThe release workflow publishes new versions from GitHub Actions with
npm provenance; the provenance shown on
npmjs.com/package/@bootgs/utils names the repository bootgs/utils,
the workflow .github/workflows/release-please.yml and the commit the version was built from. 3.0.0, the first
version under the new name, was published by hand and has a registry signature but no npm provenance; its tarball
is the same file as the attested GitHub release asset below (compare npm view @bootgs/utils@3.0.0 dist.shasum with
shasum bootgs-utils-3.0.0.tgz).
GitHub release assets. Releases from v3.0.0 on carry the npm tarball bootgs-utils-<version>.tgz and its
Sigstore build provenance bootgs-utils-<version>.tgz.sigstore.json, plus a CycloneDX SBOM of the runtime
dependency tree (sbom.cdx.json in v3.0.0, bootgs-utils-<version>.cdx.json in later releases). Earlier
releases have no assets. Verify a downloaded tarball with the GitHub CLI:
gh attestation verify bootgs-utils-<version>.tgz --repo bootgs/utils \
--signer-workflow bootgs/utils/.github/workflows/release-please.ymlAdd --bundle bootgs-utils-<version>.tgz.sigstore.json to verify against the downloaded bundle instead of fetching
the attestation from GitHub. The attestation is valid only if it was signed by the release-please.yml workflow of
bootgs/utils, which runs on pushes to main (or a manual run for an existing tag).
- No long-lived publishing credential exists: npm publishing uses
trusted publishing (OIDC) from the
npmenvironment. - No secrets are stored in the repository or its environments. Workflows use only the per-run
GITHUB_TOKEN, with permissions declared per job (release-please.ymlanddocs.ymlreferencesecrets.GITHUB_TOKEN; no other secret is referenced). Codecov uploads authenticate with OIDC. - If a secret becomes necessary, it is stored only as a GitHub Actions secret scoped to an environment, is accessible to maintainers only, and is rotated at least once a year and immediately on suspected exposure.
- GitHub secret scanning and push protection are enabled for the repository.
- Who has access to these resources: MAINTAINERS.md.
Software composition analysis (SCA).
ci.yml runs on every pull request and on pushes to main and develop:
npm audit --omit=dev --audit-level=high— a high or critical vulnerability in a runtime dependency fails thechecksjob;- the
licencesstep — a runtime dependency outside the allow-list (Apache-2.0,MIT,BSD-2-Clause,BSD-3-Clause,ISC,0BSD) fails thechecksjob.
checks is a required status check for pull requests into develop, so either failure blocks merging. Moderate
and low findings are fixed within 30 days or before the next release, whichever comes first, usually through
Dependabot updates. No release is made while an SCA violation is open.
Static analysis (SAST). CodeQL analyses JavaScript/TypeScript and GitHub Actions
on every pull request and push to main and develop and weekly; ESLint with eslint-plugin-security runs in the
checks job. High and critical CodeQL alerts are fixed before merging, medium ones before the next release. A
finding may be dismissed only as a false positive or not exploitable, with the reason written in the alert. CodeQL
is not a required status check; these thresholds are applied through maintainer review of every pull request.
- Keep dependencies updated: use the latest
@bootgs/utilsrelease and keep other packages current. - Secret management: never commit API keys or secrets; use
PropertiesServiceor another secret store. - Least privilege: declare only the OAuth scopes you need in
appsscript.json. - Input validation: validate input from users, sheets and web requests before acting on it, for example with
the library's
require*checks.
Thank you for helping us keep @bootgs/utils secure!