@legalplace/tagextractor
TagExtractor
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Internal org package; no provenance is consistent across all @legalplace/* packages. | ai | |
| phantom-deps | phantom-dep:@legalplace/lplogic | AI (phantom-deps): Same-org scoped package; phantom-dep heuristic is unreliable for internal monorepo deps. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.2.12 | 6 / 15 | |
| 3.2.7 | 6 / 15 | |
| 3.2.4 | 6 / 15 | |
| 3.2.2 | 6 / 15 |
v3.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.