@omegagrid/markdown
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/components/features/index.js | AI (source-diff): Bundled build output importing internal modules; benign. | ai | |
| source-diff | obfuscated-file:dist/components/features/blockEditMenu.js | AI (source-diff): tsc/minified build output, not true obfuscation; no malicious behavior present. | ai | |
| phantom-deps | phantom-dep:@riovir/wc-fontawesome | AI (phantom-deps): Config-only reference in a component package; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used markdown parsing library; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent pattern across all @omegagrid/* releases; no CI provenance configured for this monorepo. | ai | |
| phantom-deps | phantom-dep:@omegagrid/tabs | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@fortawesome/fontawesome-svg-core | AI (phantom-deps): Declared runtime dep referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ts-debounce | AI (phantom-deps): Declared runtime dep; phantom-dep heuristic fires on config references, stable false positive. | ai | |
| phantom-deps | phantom-dep:markdown-it | AI (phantom-deps): Declared runtime dep likely used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@omegagrid/localize | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 100 of 188)
| Version | Deps | Published |
|---|---|---|
| 0.10.60 | 9 / 11 | |
| 0.10.59 | 9 / 11 | |
| 0.10.58 | 9 / 11 | |
| 0.10.57 | 9 / 11 | |
| 0.10.56 | 9 / 11 | |
| 0.10.55 | 9 / 11 | |
| 0.10.54 | 9 / 11 | |
| 0.10.53 | 9 / 11 | |
| 0.10.52 | 9 / 11 | |
| 0.10.51 | 9 / 11 | |
| 0.10.50 | 9 / 11 | |
| 0.10.49 | 9 / 11 | |
| 0.10.48 | 9 / 11 | |
| 0.10.47 | 9 / 11 | |
| 0.10.46 | 9 / 11 | |
| 0.10.45 | 9 / 11 | |
| 0.10.44 | 9 / 11 | |
| 0.10.43 | 9 / 11 | |
| 0.10.42 | 9 / 11 | |
| 0.10.41 | 9 / 11 | |
| 0.10.37 | 9 / 11 | |
| 0.10.36 | 9 / 11 | |
| 0.10.35 | 9 / 11 | |
| 0.10.34 | 9 / 11 | |
| 0.10.33 | 9 / 11 | |
| 0.10.32 | 9 / 11 | |
| 0.10.19 | 9 / 11 | |
| 0.10.16 | 9 / 11 | |
| 0.10.4 | 9 / 11 | |
| 0.9.59 | 9 / 11 | |
| 0.9.51 | 9 / 11 | |
| 0.9.50 | 9 / 11 | |
| 0.9.48 | 9 / 11 | |
| 0.9.46 | 9 / 11 | |
| 0.9.42 | 9 / 11 | |
| 0.9.41 | 9 / 11 | |
| 0.9.31 | 9 / 11 | |
| 0.9.26 | 9 / 11 | |
| 0.9.20 | 9 / 11 | |
| 0.9.19 | 9 / 11 | |
| 0.9.14 | 9 / 11 | |
| 0.9.10 | 9 / 11 | |
| 0.9.8 | 9 / 11 | |
| 0.9.7 | 9 / 11 | |
| 0.9.0 | 9 / 11 | |
| 0.8.4 | 9 / 11 | |
| 0.7.13 | 9 / 11 | |
| 0.7.9 | 9 / 11 | |
| 0.7.0 | 9 / 11 | |
| 0.6.128 | 10 / 11 | |
| 0.6.115 | 10 / 11 | |
| 0.6.102 | 10 / 11 | |
| 0.6.98 | 10 / 11 | |
| 0.6.94 | 10 / 11 | |
| 0.6.81 | 10 / 11 | |
| 0.6.47 | 10 / 11 | |
| 0.6.45 | 10 / 11 | |
| 0.6.40 | 10 / 11 | |
| 0.6.33 | 10 / 11 | |
| 0.6.32 | 10 / 11 | |
| 0.6.31 | 10 / 11 | |
| 0.6.30 | 10 / 11 | |
| 0.6.29 | 10 / 11 | |
| 0.6.28 | 10 / 11 | |
| 0.4.0 | 10 / 11 | |
| 0.3.68 | 7 / 11 | |
| 0.3.67 | 7 / 11 | |
| 0.3.66 | 7 / 11 | |
| 0.3.65 | 7 / 11 | |
| 0.3.64 | 7 / 11 | |
| 0.3.63 | 7 / 11 | |
| 0.3.62 | 7 / 11 | |
| 0.3.61 | 7 / 11 | |
| 0.3.60 | 7 / 11 | |
| 0.3.59 | 7 / 11 | |
| 0.3.58 | 7 / 11 | |
| 0.3.57 | 7 / 11 | |
| 0.3.56 | 7 / 11 | |
| 0.3.55 | 7 / 11 | |
| 0.3.54 | 7 / 11 | |
| 0.3.53 | 7 / 11 | |
| 0.3.52 | 7 / 11 | |
| 0.3.51 | 7 / 11 | |
| 0.3.50 | 7 / 11 | |
| 0.3.49 | 7 / 11 | |
| 0.3.48 | 7 / 11 | |
| 0.3.47 | 7 / 11 | |
| 0.3.46 | 7 / 11 | |
| 0.3.45 | 7 / 11 | |
| 0.3.44 | 7 / 11 | |
| 0.3.43 | 7 / 11 | |
| 0.3.42 | 7 / 11 | |
| 0.3.41 | 7 / 11 | |
| 0.3.40 | 7 / 11 | |
| 0.3.39 | 7 / 11 | |
| 0.3.38 | 7 / 11 | |
| 0.3.37 | 7 / 11 | |
| 0.3.36 | 7 / 11 | |
| 0.3.35 | 7 / 11 | |
| 0.3.34 | 7 / 11 |
v0.10.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.