@milaboratories/pframes-rs-wasm No license 32 versions

@milaboratories/pframes-rs-wasm

npm

32

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

mike-ainseldbolotin_mipvyazankin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@milaboratories/pframes-rs-wasip2	AI (phantom-deps): Same-org WASM component dep consumed via build-time transpile (jco), not direct import; stable pattern for this package.	ai	2026/05/18
semgrep	semgrep:base64-decode	AI (semgrep): Standard jco-transpiled WASM blob compilation pattern; not a malicious payload.	ai	2026/05/03
source-diff	encoded-string-file:dist/generated/pframes_rs_wasm.js	AI (source-diff): Base64 strings are inlined WASM modules produced by jco transpile; stable pattern for this package.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Internal @milaboratories tooling package; sparse metadata is expected for org-internal WASM packages.	ai	2026/04/29
npm-metadata	no-description	AI (npm-metadata): Org-internal package; missing description is a style issue, not a risk signal.	ai	2026/04/29
phantom-deps	phantom-dep:@milaboratories/pframes-rs-wasi	AI (phantom-deps): Same-org WASI dependency; phantom-dep heuristic fires because it's a runtime dep bundled/transpiled rather than directly imported.	ai	2026/04/29

Versions (showing 32 of 32)

Version	Deps	Published
1.1.37	1 / 12	2026-05-25
1.1.36	1 / 12	2026-05-18
1.1.35	1 / 12	2026-05-12
1.1.34	1 / 12	2026-05-08
1.1.33	1 / 12	2026-05-06
1.1.31	1 / 12	2026-04-29
1.1.30	1 / 12	2026-04-28
1.1.29	1 / 12	2026-04-27
1.1.27	0 / 12	2026-04-23
1.1.26	0 / 12	2026-04-23
1.1.25	0 / 12	2026-04-22
1.1.24	0 / 12	2026-04-22
1.1.22	0 / 12	2026-04-20
1.1.21	0 / 12	2026-04-20
1.1.20	0 / 12	2026-04-17
1.1.19	0 / 12	2026-04-17
1.1.18	0 / 12	2026-04-07
1.1.17	0 / 12	2026-04-01
1.1.16	0 / 12	2026-03-30
1.1.15	0 / 12	2026-03-23
1.1.14	0 / 12	2026-03-12
1.1.13	0 / 12	2026-03-10
1.1.12	0 / 11	2026-03-05
1.1.11	0 / 11	2026-03-02
1.1.10	0 / 11	2026-02-24
1.1.9	0 / 11	2026-02-23
1.1.8	0 / 11	2026-02-23
1.1.7	0 / 11	2026-02-18
0.1.3	0 / 11	2026-02-17
0.1.2	0 / 11	2026-02-13
0.1.1	0 / 7	2026-02-11
0.1.0	0 / 7	2026-02-09

v1.1.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.29

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.25

2 findings

HIGH Long encoded string in modified file: dist/generated/pframes_rs_wasm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.24

2 findings

HIGH Long encoded string in modified file: dist/generated/pframes_rs_wasm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.22

2 findings

HIGH Long encoded string in modified file: dist/generated/pframes_rs_wasm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.21

2 findings

HIGH Long encoded string in modified file: dist/generated/pframes_rs_wasm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.20

2 findings

HIGH Long encoded string in modified file: dist/generated/pframes_rs_wasm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.19

2 findings

HIGH Long encoded string in modified file: dist/generated/pframes_rs_wasm.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.