iwer
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Likely org co-maintainer add for Meta-owned repo; no other malicious signal. | ai | |
| provenance | missing-githead | AI (provenance): Metadata-only regression, no behavior change; publisher track record is clean. | ai | |
| dependencies | unvetted-dep:webxr-layers-polyfill | AI (dependencies): webxr-layers-polyfill is a well-known WebXR polyfill; stable dependency for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 2 / 12 | |
| 2.2.1 | 2 / 24 | |
| 2.2.0 | 2 / 24 | |
| 2.1.1 | 2 / 23 | |
| 2.1.0 | 2 / 23 | |
| 2.0.1 | 1 / 23 | |
| 2.0.0 | 1 / 23 |
v2.3.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: felixtrz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
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.