@inploi/plugin-kin
Kin - A unified Talent Agent interface for hiring. One system, many roles.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:streamdown | AI (phantom-deps): streamdown is a declared runtime dep; phantom-dep heuristic fires but it is legitimately bundled into dist output. | ai | |
| phantom-deps | phantom-dep:@inploi/colors | AI (phantom-deps): Same-org dep likely consumed indirectly via bundled output; stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 2 / 14 | |
| 2.7.8 | 2 / 14 | |
| 2.3.2 | 2 / 10 | |
| 2.3.1 | 2 / 10 | |
| 2.3.0 | 2 / 10 | |
| 2.2.0 | 2 / 10 | |
| 2.1.1 | 2 / 10 | |
| 2.1.0 | 2 / 10 | |
| 2.0.0 | 2 / 10 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.