@milaboratories/pl-tree
Reactive pl tree state
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 | publisher-changed | AI (provenance): mike-ainsel is an established @milaboratories org publisher with 993 approved packages; internal handoff within same org. | ai | |
| phantom-deps | phantom-dep:@milaboratories/pl-error-like | AI (phantom-deps): Same-org dependency in a monorepo; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established org package with 158 versions; no script/dep changes; dormancy likely reflects normal dev cadence, not takeover. | ai | |
| dependencies | unvetted-dep:@milaboratories/computable | AI (dependencies): Same @milaboratories namespace; sibling package consistent with this org's ecosystem. | ai | |
| dependencies | unvetted-dep:@milaboratories/ts-helpers | AI (dependencies): Same @milaboratories namespace; sibling package consistent with this org's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established org package with 157 versions; lack of Sigstore provenance is consistent across all releases. | ai |
Versions (showing 25 of 126)
| Version | Deps | Published |
|---|---|---|
| 1.7.11 | 8 / 8 | |
| 1.7.10 | 8 / 8 | |
| 1.7.9 | 8 / 8 | |
| 1.7.8 | 8 / 8 | |
| 1.7.7 | 8 / 8 | |
| 1.7.6 | 8 / 8 | |
| 1.7.5 | 8 / 7 | |
| 1.7.4 | 8 / 7 | |
| 1.7.3 | 8 / 7 | |
| 1.7.2 | 8 / 7 | |
| 1.7.1 | 8 / 7 | |
| 1.7.0 | 8 / 7 | |
| 1.6.12 | 8 / 7 | |
| 1.6.11 | 8 / 7 | |
| 1.6.10 | 8 / 7 | |
| 1.6.9 | 8 / 7 | |
| 1.6.8 | 8 / 7 | |
| 1.6.7 | 8 / 7 | |
| 1.6.6 | 8 / 7 | |
| 1.6.5 | 8 / 7 | |
| 1.6.4 | 8 / 7 | |
| 1.6.3 | 8 / 7 | |
| 1.6.2 | 8 / 7 | |
| 1.6.1 | 8 / 7 | |
| 1.6.0 | 8 / 7 |
v1.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.