@kne/remote-loader
11
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
lingtongyangwang123456juliewangmetacoo
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all 44 versions; publisher does not use Sigstore attestation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.4.6 | 3 / 14 | |
| 1.4.5 | 3 / 14 | |
| 1.4.4 | 3 / 14 | |
| 1.4.3 | 3 / 14 | |
| 1.4.2 | 3 / 14 | |
| 1.4.1 | 3 / 14 | |
| 1.4.0 | 3 / 14 | |
| 1.3.3 | 3 / 14 | |
| 1.3.2 | 3 / 14 | |
| 1.3.1 | 3 / 14 | |
| 1.3.0 | 3 / 14 |
v1.3.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.