indefinite-observable
<!-- TODO: update version number before releasing, here and in the script tag --> [](https://www.npmjs.com/package/indefinite-observable/v/2.0.1) [ relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/indefinite-observable.bundle.js | AI (source-diff): Rollup bundle of symbol-observable ponyfill; dynamic checks and global detection patterns are standard UMD boilerplate, not malware. | ai | |
| provenance | missing-githead | AI (provenance): Major version bump with tooling changes; publisher is the original author with clean history since package inception. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 1 / 19 | |
| 2.0.0 | 1 / 19 | |
| 1.0.2 | 1 / 15 | |
| 1.0.1 | 1 / 13 | |
| 0.3.0 | 1 / 13 | |
| 0.2.0 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 0.0.0 | 1 / 4 |
v2.0.1
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: appsforartists.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: appsforartists.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.