@flint.fyi/markdown-language
[Experimental] Markdown language for Flint.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | slsa-provenance | AI (provenance): Package consistently publishes via CI with Sigstore attestation; stable supply-chain integrity signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped experimental package under flint.fyi org; sparse README is expected for an internal/experimental library. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Experimental monorepo package from established publisher; 0.0.0 reflects early-stage scoped package, not malicious intent. | ai | |
| phantom-deps | phantom-dep:@types/mdast | AI (phantom-deps): @types/mdast is a type-only dependency used transitively; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@types/unist | AI (phantom-deps): @types/unist is a type-only dependency used transitively; not directly imported at runtime. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.15.3 | 8 / 2 | |
| 0.15.2 | 8 / 2 | |
| 0.15.1 | 8 / 2 | |
| 0.15.0 | 6 / 3 | |
| 0.0.0 | 6 / 3 |
v0.15.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.