| Safe Haskell | None |
|---|---|
| Language | GHC2021 |
Ecluse.Core.Osv.Ecosystem
Description
What one OSV compile pass needs to know about the ecosystem it compiles.
osv.dev and Écluse do not always agree on the spelling, so a pass that carried one name would either fetch a directory that does not exist or write an artifact the proxy's sync refuses. The pass also needs the version grammar that orders the advisory bounds it ingests, and the fan-out an ordinary advisory of the feed stays under.
Synopsis
Documentation
data OsvEcosystem Source #
The two spellings, the version grammar, and the fan-out bound one compile pass needs.
Constructors
| OsvEcosystem | |
Fields
| |
Instances
| Show OsvEcosystem Source # | |
Defined in Ecluse.Core.Osv.Ecosystem Methods showsPrec :: Int -> OsvEcosystem -> ShowS # show :: OsvEcosystem -> String # showList :: [OsvEcosystem] -> ShowS # | |
| Eq OsvEcosystem Source # | |
Defined in Ecluse.Core.Osv.Ecosystem | |
osvEcosystemFor :: Ecosystem -> OsvEcosystem Source #
An ecosystem's pair of spellings. npm agrees with osv.dev, PyPI and RubyGems do not.
>>>osvEcosystemFor PyPIOsvEcosystem {osvExportDirectory = "PyPI", osvWireName = "pypi", osvEcosystemTag = Just PyPI, osvMaxAdvisoryFanOut = 4096}
osvEcosystemNamed :: Text -> OsvEcosystem Source #
The pair for a name a one-shot compile was given: a name this build serves resolves through
osvEcosystemFor, and any other spells itself on both halves.
>>>osvEcosystemNamed "pypi"OsvEcosystem {osvExportDirectory = "PyPI", osvWireName = "pypi", osvEcosystemTag = Just PyPI, osvMaxAdvisoryFanOut = 4096}