Clarification requested for historical modified: 0001-01-01T00:00:00Z values
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation, security
Research direction
Start by reviewing the affected advisory records and the repository's OSV-schema handling, if present. Determine whether the timestamp is authoritative or a sentinel, then identify whether the appropriate resolution is correcting records or documenting the semantics. Done means the repository's position is authoritative and the affected data or documentation is updated accordingly.
Written by the indexing model from the issue text.
Description
Hello,
We are consuming the Python Software Foundation advisory database using the OSV schema and encountered historical advisory records where:
modified: 0001-01-01T00:00:00Z
Could you please clarify whether this value represents:
- the literal authoritative modification timestamp, or
- an unknown/unavailable modification date represented by a sentinel value?
If it is intended as a sentinel, could the affected records be corrected or the intended semantics be documented?
Our validation pipeline preserves upstream chronology and therefore cannot safely infer or replace this timestamp without authoritative clarification.
This currently blocks deterministic admission of the affected advisory data.
Thank you.
- Dominant language
- Python
- Stars
- 49
- Forks
- 14
- Avg merge
- 4h 44m
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from psf/advisory-database
-
Maintain all fixed versions on CVE record after upstream git branches are deletedMay be free again @sethmlarson claimed this 190 days ago, and no pull request is open. Open
psf/advisory-database#121 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
psf/advisory-database#77 · 1 reaction ·
Maintainers usually reply within 1 day
-
Consider providing a template for record feedbackPossibly taken @speco29 claimed this 354 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
psf/advisory-database#60 · 1 comment ·
Maintainers usually reply within 1 day
All issues in psf/advisory-database
Similar issues
-
plot_graph crashes when a mesh node has no m2m edgePossibly taken @tygvi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mllam/neural-lam#883 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement possible-duplicate
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
AOSSIE-Org/PictoPy#1715 · 2 comments ·
Maintainers usually reply within 6 days
-
SQLite connector omits generated columns from the catalog, and drops relationships sourced on themOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NVIDIA/auto-ontology#511 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ethereum/execution-specs#3996 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cpp-best-practices/project_validator#267 ·
Maintainers usually reply within 1 day