@apimatic/convert-to-stream
converts the content to stream
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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Stale change, long unremoved, trusted publisher track record. | ai | |
| provenance | missing-githead | AI (provenance): Metadata-only regression on trusted publisher; no malicious behavior. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Legitimate long-lived package's genuine v0.0.0 initial release, not a throwaway. | ai | |
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): Standard Istanbul/nyc coverage report artifact (Google Prettify); not malicious, expected from jest --coverage runs. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.9 | 1 / 8 | |
| 0.1.8 | 1 / 8 | |
| 0.1.7 | 1 / 8 | |
| 0.1.6 | 1 / 8 | |
| 0.1.5 | 1 / 8 | |
| 0.1.4 | 1 / 8 | |
| 0.1.3 | 0 / 8 | |
| 0.1.2 | 0 / 8 | |
| 0.1.0 | 0 / 8 | |
| 0.0.2 | 0 / 6 | |
| 0.0.1 | 0 / 4 | |
| 0.0.0 | 0 / 4 |
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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: maryamadnan3.
This version was published by a different npm account (maryamadnan3) than the most recent previously approved version (wajahatiqbal) on 2023-04-04. It has since remained available on npm for 1206 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
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: wajahatiqbal.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.