Skip to content
StandardsSoftware and supply chainConformance
Software and supply chain

Software and supply chain: conformance

How an implementer in software and supply chain demonstrates conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. Each result names its evaluator and the time of evaluation, and each artefact is identified by a UNI (Unique Nexus Identifier).

Software and supply chain
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-1, NS-11, NS-12.
  • Open standards: SPDX specification; CycloneDX Bill of Materials (ECMA-424); Supply-chain Levels for Software Artifacts (SLSA); in-toto Attestation Framework; Sigstore (Cosign, Fulcio, Rekor); Common Security Advisory Framework (CSAF) 2.0; OpenVEX specification; Open Source Vulnerability (OSV) schema.
  • Data and feeds: OSV.dev vulnerability API; NVD CVE API 2.0; Rekor public transparency log.
  • Couples with: Deployment services; Verification and monitoring; AI, models and agents; Provenance and evidence.
01ઝાંખી

Summary

  1. 01Self-assessmentagainst the rules
  2. 02Clause setNS-10
  3. 03Evidencereferenced, not embedded
  4. 04AttestationNS-11, named evaluator
  5. 05Reportgenerated from results
Nexus Standards
3
NS-1, NS-11, NS-12
Open standards
8
named, never copied
Data and feeds
3
listed for reference
Couplings
4
with other areas
02આવરણ

Standards listed in the cross-cutting capabilities tier

The programme areas of this tier against the standards they list in the registry; the row for this area sets the initial scope of a self-assessment.

Coverage matrix · standards across, programme areas downNexus Standards registry
28 of 210 programme and standard pairs are listed, across 14 programmes and 15 standards. Source: Nexus Standards programme register and standards index.

Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.

03The baseline

Conformance to NS-0

An implementation conforms to NS-0 when it:

  • names the canonical repository and the versions of the standards it applies;
  • does not fork a registry;
  • runs the repository validator, or an equivalent, on the copies of the registries it uses;
  • records its implementation status per standard in registry/consumers.yaml truthfully; and
  • carries the honesty fields (legalState, claimCeiling, status) on every record it publishes.

Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.

04Self-assessment

Initial self-assessment for software and supply chain

The first rules of each applicable standard. A self-assessment is a statement by the implementer, verifiable under NS-11.

નિયમRequirementધોરણ
NS12-R1Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version.NS-12
NS12-R2Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI.NS-12
NS12-R3Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify.NS-12
05NS-11 · Attestations

Attestations

One attestation is recorded per clause, per subject, per evaluation (AT category, append-only). Results: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause’s selectors at that instant); REFUSED (the evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and, optionally, a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.

Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.

06NS-11 · Monitoring

દેખરેખ

Monitoring is continuous evaluation together with observation records. For each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation, and why), (c) drift (a change in a subject’s records that invalidates an attestation) and (d) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.

07NS-11 · Reporting

Reporting

A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artefacts (RP) and may be published (NS-8) only when their legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.

08NS-14 · claims

Display of conformance statements

A context (NS-9) or artefact claims a relation to an external standard only through a clause set (NS-10) that cites that standard and is evaluated (NS-11). The claim is displayed as "implements clauses derived from <standard> (n of m with a current PASS)", with attestation UNIs. It is never displayed as "compliant with" or "certified to" unless a decision of the body entitled to say so is referenced. Where a body operates its own certification, conformance under the Nexus Standards is explicitly not that certification.

09પ્રશ્નો

પ્રશ્નો અને જવાબો.

How does a conformance report in software and supply chain relate to the decisions of other bodies?
A conformance report states clause results and their evidence. Where a decision of an authority or another body is relevant, the report cites it by reference.
What happens when evidence is missing?
The attestation is recorded as indeterminate rather than as a pass. Missing evidence, rights state or verification results in a reasoned refusal (NS0-P12).
ધોરણો

Shape the standards for software and supply chain.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

સ્થિતિ અને ઉપયોગ. Nexus Standards એ NS-13 હેઠળ ખુલ્લી પ્રક્રિયા દ્વારા વિકસાવાયેલાં અને સ્વૈચ્છિક ઉપયોગ માટે પ્રકાશિત પ્રસ્તાવિત ધોરણો છે; તે પ્રમાણન, માન્યતા કે નિયમનકારી મંજૂરી નથી, અને અપનાવવું વૈશ્વિક ધોરણો પરિષદનો અને, દરેક દેશમાં, તેની રાષ્ટ્રીય ધોરણો પરિષદનો નિર્ણય રહે છે. UNI (Unique Nexus Identifier) કલાકૃતિને ઓળખે છે; તે તેને પ્રમાણિત કરતું નથી. ધોરણ સંસ્થાઓ અને તેમનાં ધોરણોનાં નામ તેમના સંરક્ષકોનાં છે અને ફક્ત દસ્તાવેજોને ઓળખવા વપરાય છે; અહીં કોઈ બાહ્ય ધોરણનું લખાણ પુનઃઉત્પાદિત કરાયું નથી. Nexus Standards અહીં નામાંકિત કોઈ ધોરણ સંસ્થા સાથે સંલગ્ન, તેના દ્વારા સમર્થિત કે પ્રમાણિત નથી.

લાઇસન્સ: ધોરણોના લખાણ, રજિસ્ટ્રીઓ, સ્કીમા અને ડેટા માટે CC BY 4.0; સંદર્ભ કોડ માટે Apache-2.0. બાહ્ય ધોરણો તેમનાં પોતાનાં લાઇસન્સ હેઠળ નામ, ક્રમાંક અને લિંક દ્વારા ટાંકવામાં આવે છે. તૃતીય-પક્ષ ડેટા, લાઇબ્રેરીઓ અને ફૉન્ટ તેમનાં પોતાનાં લાઇસન્સ જાળવે છે: તૃતીય-પક્ષ સૂચનાઓ જુઓ.