@mdit/plugin-attrs
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.js | AI (source-diff): Content is standard minified plugin code, not obfuscated malware; long lines are expected in bundled dist output. | ai | |
| phantom-deps | phantom-dep:@mdit/helper | AI (phantom-deps): Same-org scoped helper; likely used transitively or in build, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): Type-only dependency; not imported at runtime by design. | ai | |
| source-diff | obfuscated-file:lib/browser.js | AI (source-diff): browser.js is a standard Rollup minified bundle for a markdown-it plugin; not obfuscated malware. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.0.2 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 | |
| 0.25.2 | 2 / 2 | |
| 0.25.1 | 2 / 1 | |
| 0.24.2 | 2 / 2 | |
| 0.24.1 | 2 / 2 | |
| 0.24.0 | 2 / 2 | |
| 0.23.3 | 2 / 2 | |
| 0.23.2 | 2 / 2 | |
| 0.23.1 | 2 / 2 | |
| 0.23.0 | 2 / 2 | |
| 0.22.0 | 2 / 2 | |
| 0.21.0 | 2 / 2 | |
| 0.20.0 | 2 / 2 | |
| 0.19.0 | 2 / 2 | |
| 0.18.0 | 2 / 2 | |
| 0.17.0 | 2 / 2 | |
| 0.16.7 | 2 / 2 | |
| 0.16.6 | 2 / 2 | |
| 0.16.2 | 2 / 2 | |
| 0.16.1 | 2 / 2 | |
| 0.16.0 | 2 / 2 | |
| 0.15.1 | 2 / 2 | |
| 0.15.0 | 2 / 2 | |
| 0.14.0 | 2 / 2 | |
| 0.13.1 | 1 / 2 | |
| 0.13.0 | 1 / 2 |
v1.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.