DFSG NEW Queue

DFSG, Licensing & New Packages Team

sarif-oasis-schemas 2.1.0+errata01-1

Package Information

DescriptionOASIS SARIF 2.1.0 JSON schemas

The Static Analysis Results Interchange Format (SARIF) 2.1.0 is the OASIS standard for the output of static analysis tools and vulnerability scanners. This package ships the two JSON schemas that the OASIS Standard publishes as part of its Work Product: one for a SARIF log and one for an external property file. Tools use them to check that a log conforms to the standard, for example with check-jsonschema.

The files are installed in /usr/share/sarif/schemas.

This package is in non-free because the OASIS Standard notice that covers the schemas permits verbatim copying but forbids modification, which the Debian Free Software Guidelines require.

MaintainerJuan Manuel Méndez Rey <juan.mendezr@proton.me>
Changed ByJuan Manuel Méndez Rey <juan.mendezr@proton.me>
Sponsortsimonq2@debian.org
Distributionunstable
Architectureall
VCSgit: https://salsa.debian.org/mendezr/sarif-oasis-schemas.git (browse)
Closes#1153015
Trackerhttps://tracker.debian.org/pkg/sarif-oasis-schemas
Uploaded1 day ago

New Package Report

.changes◂
Architecturesource all
Distributionunstable
DateWed, 04 Nov 2026 13:30:00 +0100
Sourcesarif-oasis-schemas
Version2.1.0+errata01-1
Changed-ByJuan Manuel Méndez Rey <juan.mendezr@proton.me>
Changelog◂
sarif-oasis-schemas (2.1.0+errata01-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1153015)
.dsc◂
Componentnon-free
Package-Listsarif-oasis-schemas deb non-free/misc optional arch=all
Sectionnon-free/misc
Priorityoptional
debian/copyright◂
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: SARIF 2.1.0 JSON schemas
Upstream-Contact: https://github.com/oasis-tcs/sarif-spec/issues
Source: https://docs.oasis-open.org/sarif/sarif/v2.1.0/errata01/os/schemas/
Comment: The two files are the ones that the SARIF Version 2.1.0 Plus Errata
 01 OASIS Standard names as components of its Work Product. The license below
 is the Notices section of that standard, reproduced without changes, which is
 the condition under which the files may be copied.

Files: *
Copyright: 2023 OASIS Open
License: OASIS-Standard-Notice

Files: debian/*
Copyright: 2026 Juan Manuel Méndez Rey <juan.mendezr@proton.me>
License: Expat
Comment: The packaging is free; the schemas it installs are not.

License: OASIS-Standard-Notice
 Copyright © OASIS Open 2023. All Rights Reserved.
 .
 All capitalized terms in the following text have the meanings assigned to
 them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR
 Policy"). The full Policy may be found at the OASIS website:
 [https://www.oasis-open.org/policies-guidelines/ipr/].
 .
 This document and translations of it may be copied and furnished to others,
 and derivative works that comment on or otherwise explain it or assist in
 its implementation may be prepared, copied, published, and distributed, in
 whole or in part, without restriction of any kind, provided that the above
 copyright notice and this section are included on all such copies and
 derivative works.
 .
 However, this document itself may not be modified in any way, including by
 removing the copyright notice or references to OASIS, except as needed for
 the purpose of developing any document or deliverable produced by an OASIS
 Technical Committee (in which case the rules applicable to copyrights, as
 set forth in the OASIS IPR Policy, must be followed) or as required to
 translate it into languages other than English.
 .
 The limited permissions granted above are perpetual and will not be revoked
 by OASIS or its successors or assigns.
 .
 This document and the information contained herein is provided on an "AS
 IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL
 NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF
 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS AND ITS MEMBERS
 WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL
 DAMAGES ARISING OUT OF ANY USE OF THIS DOCUMENT OR ANY PART THEREOF.
 .
 As stated in the OASIS IPR Policy, the following three paragraphs in
 brackets apply to OASIS Standards Final Deliverable documents (Committee
 Specifications, OASIS Standards, or Approved Errata).
 .
 [OASIS requests that any OASIS Party or any other party that believes it
 has patent claims that would necessarily be infringed by implementations of
 this OASIS Standards Final Deliverable, to notify OASIS TC Administrator
 and provide an indication of its willingness to grant patent licenses to
 such patent claims in a manner consistent with the IPR Mode of the OASIS
 Technical Committee that produced this deliverable.]
 .
 [OASIS invites any party to contact the OASIS TC Administrator if it is
 aware of a claim of ownership of any patent claims that would necessarily
 be infringed by implementations of this OASIS Standards Final Deliverable
 by a patent holder that is not willing to provide a license to such patent
 claims in a manner consistent with the IPR Mode of the OASIS Technical
 Committee that produced this OASIS Standards Final Deliverable. OASIS may
 include such claims on its website, but disclaims any obligation to do so.]
 .
 [OASIS takes no position regarding the validity or scope of any
 intellectual property or other rights that might be claimed to pertain to
 the implementation or use of the technology described in this OASIS
 Standards Final Deliverable or the extent to which any license under such
 rights might or might not be available; neither does it represent that it
 has made any effort to identify any such rights. Information on OASIS'
 procedures with respect to rights in any document or deliverable produced
 by an OASIS Technical Committee can be found on the OASIS website. Copies
 of claims of rights made available for publication and any assurances of
 licenses to be made available, or the result of an attempt made to obtain a
 general license or permission for the use of such proprietary rights by
 implementers or users of this OASIS Standards Final Deliverable, can be
 obtained from the OASIS TC Administrator. OASIS makes no representation
 that any information or list of intellectual property rights will at any
 time be complete, or that any claims in such list are, in fact, Essential
 Claims.]
 .
 The name "OASIS" is a trademark of OASIS, the owner and developer of this
 document, and should be used only to refer to the organization and its
 official outputs. OASIS welcomes reference to, and implementation and use
 of, documents, while reserving the right to enforce its marks against
 misleading uses. Please see
 https://www.oasis-open.org/policies-guidelines/trademark/ for above
 guidance.

License: Expat
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:
 .
 The above copyright notice and this permission notice shall be included in
 all copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.

DFSG Assistant LLM REVIEW 0 blocker, 1 important, 0 minor

This is an LLM based review using a Debian Inference based workflow. It was not written by a member of the DFSG team and has not been checked by one. It is not a decision on the package: it may be wrong, and it may have missed things.

Reviewed 1 day ago.

Report◂

DFSG NEW review for sarif-oasis-schemas version 2.1.0+errata01-1

Summary

  • Licensing is DFSG-compliant and debian/copyright is accurate: No
  • Packaging is of good quality: Yes
  • Issues: 0 blocker, 1 important, 0 minor
  • debian/watch: version 5, refused by the checks made before uscan is run
  • debian/copyright: machine-readable
  • Scan before the review: nothing found

Licensing

The licensing is not DFSG-free, and the package says so: the OASIS notice covering the two schemas allows verbatim copying but states that the document 'may not be modified in any way', which fails DFSG 3 (modification and derived works are required). The package is correctly in non-free/misc and its Description explains why. debian/copyright is accurate and complete for every file: Files: * names the only upstream holder, '2023 OASIS Open', and reproduces the OASIS notice in full (it is not in /usr/share/common-licenses); Files: debian/* covers the packaging under Expat with the full text. Nothing needs changing on licensing; the question is answered 'no' only because the schema licence itself is non-free, as intended.

Packaging

Small and carefully packaged: minimal dh $@ rules at compat 14 (the recommended level), arch:all with Multi-Arch: foreign, correct dependencies, a meaningful autopkgtest, a reproducibly generated orig tarball documented in debian/README.source, DEP-5 copyright, Vcs-* fields and a sane changelog. Standards-Version 4.7.4 matches the reviewing system's Policy 4.7.4.1 (first two components). The only oddity is a trailing comma in Build-Depends and in Depends; dpkg tolerates it (dpkg-source normalised it in the .dsc, and the empty ${misc:Depends} leaves an empty field that dpkg-gencontrol drops), so it is cosmetic only and not reported as an issue.

Issues

important packaging 1. debian/watch was refused by the checks made before uscan is run ◂
  • Files: debian/watch
  • Basis: found by the review tooling's own checks
  • Evidence: - it names no upstream URL or template
  • Problem: These checks refuse what is not plausibly a watch file, and the values known to make uscan do something other than look at an upstream site. uscan was not run, so the file is untested.
  • Fix: Read debian/watch and correct it. If uscan is run on it by hand, do that with caution.
Verified ◂
  • Whole tree covered: two upstream files (sarif-schema-2.1.0.json, sarif-external-property-file-schema-2.1.0.json) and all of debian/ (control, copyright, rules, changelog, install, README.source, make-orig.sh, gbp.conf, salsa-ci.yml, source/format, tests/control, tests/validate, upstream/metadata), plus the .dsc and the two tarballs. No generated, minified, binary, font, image or PDF files exist, and the prescan listed none.
  • The two JSON files carry no licence or copyright notice of their own: a grep for copyright/licence/OASIS in both finds only the id/$id schema URLs, so the OASIS notice reproduced in debian/copyright is the only statement of their terms.
  • debian/copyright is DEP-5: Files: * (schemas) names holder '2023 OASIS Open' and the full OASIS notice, which is not in /usr/share/common-licenses and is therefore included in full; Files: debian/* gives Expat with its full text. The only holder the prescan found, OASIS Open, is named.
  • The OASIS notice forbids modifying the document ('this document itself may not be modified in any way'), which fails DFSG 3; Section non-free/misc and the Description state this, so the package is correctly in non-free rather than main.
  • Tarballs match the unpacked tree: the orig tarball holds exactly the two schema files under sarif-oasis-schemas-2.1.0+errata01/, the debian tarball the debian/ directory, and the .dsc names those two tarballs.
  • debian/control: Build-Depends only on debhelper-compat (= 14); no missing or over-tight dependencies; the binary stanza is arch:all + Multi-Arch: foreign and needs no runtime dependencies. The trailing comma after debhelper-compat (= 14) is harmless (dpkg-source emitted the .dsc without it).
  • debian/changelog: version 2.1.0+errata01-1, distribution unstable, a well-formed initial-release entry closing #1153015, and the date (Wed, 04 Nov 2026) is consistent.
  • Autopkgtest present and real: debian/tests/control depends on python3-check-jsonschema (which exists in the archive, 0.34.1+really0.25.0-3) and @, and debian/tests/validate checks both schemas against their metaschemas and validates a good and a deliberately bad SARIF instance.
  • Standards-Version 4.7.4 against Policy 4.7.4.1: current (same first two components); compat 14 is the recommended debhelper level; debian/rules is the minimal dh $@; no patches, maintainer scripts or compiled code, so no hardening or patch-management concerns.
  • debian/make-orig.sh documents and reproduces the orig tarball (sorted names, fixed owner/mode/mtime), and debian/README.source records the two files' SHA256 and why there is no upstream tarball; the packaging files are covered by the Expat stanza.
Not confirmed ◂
  • The SHA256 sums recorded in debian/README.source could not be recomputed (no hashing tool available), and the OASIS manifest was not consulted (no network), so the files' bytes are taken as shipped.
  • The OASIS notice quoted in debian/copyright could not be compared with the published standard online.
  • No build or autopkgtest was run; the review assumes both succeed.
Proposed changes ◂

None.

Uploader's response to the LLM review

Explanation:

OASIS publishes the two schemas as separate JSON files, with no release tarball, so there is nothing for uscan to
fetch. debian/make-orig.sh builds the orig, and debian/README.source has the
checksums, which match the OASIS manifest.

Fixed in git with the form uscan(1) documents for this case:

Version: 5
Untrackable: OASIS publishes the schemas as separate JSON files, ...

https://salsa.debian.org/mendezr/sarif-oasis-schemas/-/commit/d8e2101

uscan recognises it and lintian --pedantic is clean.

It only changes how new versions are tracked, so I'd keep it for the next upload rather than
re-upload during NEW, unless you prefer otherwise.

— Juan Manuel Méndez Rey (mendezr), 1 day ago

Back to Dashboard | View all reviews for this package