@plotdb/block
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() evaluates user-supplied block scripts at runtime — documented plugin pattern for this package, not supply-chain risk. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in a standard i18n Proxy handler; not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): Established package with public repo; lack of Sigstore provenance is common and not a disqualifier here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.7.2 | 5 / 32 | |
| 5.7.1 | 5 / 32 | |
| 5.7.0 | 5 / 32 | |
| 5.6.5 | 5 / 31 | |
| 5.6.4 | 5 / 31 | |
| 5.6.3 | 5 / 31 | |
| 5.6.2 | 5 / 31 | |
| 5.6.1 | 5 / 31 | |
| 5.6.0 | 5 / 31 |
v5.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.