Skip to content
SLSA

Slot: attestation_storage_uri

Where the signed attestation is stored or can be fetched.

URI: slsa:attestation_storage_uri

Applicable Classes

Section titled “Applicable Classes”
Name Description Modifies Slot
SlsaStatement An in-toto statement with the fields this schema adds: where the signed attes… no

Properties

Section titled “Properties”

Type and Range

Section titled “Type and Range”
Property Value
Range Uri
Domain Of SlsaStatement

Slot Characteristics

Section titled “Slot Characteristics”
Property Value
Owner SlsaStatement

In Subsets

Section titled “In Subsets”

Comments

Section titled “Comments”
  • SLSA asks producers to publish attestations in at least one place and preferably more: beside the source repository’s releases, beside the artifact in its package registry, which it prefers in the long term, or elsewhere with an entry in a transparency log.
  • Where to store attestations was an open question for practitioners (Tamanna et al., 2024, LF.1).

Identifier and Mapping Information

Section titled “Identifier and Mapping Information”

Schema Source

Section titled “Schema Source”

Mappings

Section titled “Mappings”
Mapping Type Mapped Value
self slsa:attestation_storage_uri
native slsa:attestation_storage_uri

LinkML Source

Section titled “LinkML Source”
name: attestation_storage_uri
description: Where the signed attestation is stored or can be fetched.
comments:
- 'SLSA asks producers to publish attestations in at least one place and preferably
  more: beside the source repository''s releases, beside the artifact in its package
  registry, which it prefers in the long term, or elsewhere with an entry in a transparency
  log.'
- Where to store attestations was an open question for practitioners (Tamanna et al.,
  2024, LF.1).
in_subset:
- slsa_adoption_study
from_schema: https://w3id.org/lmodel/slsa
rank: 1000
owner: SlsaStatement
domain_of:
- SlsaStatement
range: uri