@milaboratories/pl-errors
Parsing errors from Pl backend
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): mike-ainsel is an established publisher in the same org with 915 approved packages; transition appears legitimate. | ai | |
| dependencies | unvetted-dep:@milaboratories/ts-helpers | AI (dependencies): Internal org dependency from the same @milaboratories namespace; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 102 versions of this package; org does not use Sigstore attestation. | ai |
Versions (showing 40 of 140)
| Version | Deps | Published |
|---|---|---|
| 1.1.30 | 3 / 7 | |
| 1.1.29 | 3 / 7 | |
| 1.1.28 | 3 / 7 | |
| 1.1.27 | 3 / 7 | |
| 1.1.26 | 3 / 7 | |
| 1.1.25 | 3 / 7 | |
| 1.1.24 | 3 / 7 | |
| 1.1.23 | 3 / 7 | |
| 1.1.22 | 3 / 7 | |
| 1.1.21 | 3 / 7 | |
| 1.1.20 | 3 / 7 | |
| 1.1.19 | 3 / 7 | |
| 1.1.18 | 3 / 7 | |
| 1.1.17 | 3 / 7 | |
| 1.1.16 | 3 / 7 | |
| 1.1.15 | 3 / 6 | |
| 1.1.14 | 3 / 6 | |
| 1.1.13 | 3 / 6 | |
| 1.1.12 | 3 / 6 | |
| 1.1.11 | 3 / 6 | |
| 1.1.10 | 3 / 6 | |
| 1.1.9 | 3 / 6 | |
| 1.1.8 | 3 / 6 | |
| 1.1.7 | 3 / 6 | |
| 1.1.6 | 3 / 6 | |
| 1.1.5 | 3 / 6 | |
| 1.1.4 | 3 / 6 | |
| 1.1.3 | 3 / 6 | |
| 1.1.2 | 3 / 6 | |
| 1.1.1 | 3 / 6 | |
| 1.1.0 | 3 / 6 | |
| 1.0.9 | 3 / 6 | |
| 1.0.8 | 3 / 6 | |
| 1.0.7 | 3 / 6 | |
| 1.0.6 | 3 / 6 | |
| 1.0.5 | 3 / 6 | |
| 1.0.4 | 3 / 6 | |
| 1.0.3 | 2 / 5 | |
| 1.0.2 | 2 / 5 | |
| 1.0.1 | 2 / 5 |
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.
v1.0.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.