@supernova-studio/pulsar-core
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): punycode is a well-known stdlib polyfill; no malicious indicators in this addition. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is consistent with org automation; stable for this package going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): sn-filipdanisko addition aligns with the org's CI migration; no malicious indicators. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established 350-version package; sparse README/keywords are a known pattern for this SDK component. | ai | |
| phantom-deps | phantom-dep:dot-prop | AI (phantom-deps): dot-prop declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:ts-dedent | AI (phantom-deps): ts-dedent declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:jsep | AI (phantom-deps): jsep is declared in dependencies and used via config; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jsep-plugin/object | AI (phantom-deps): @jsep-plugin/object declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@jsep-plugin/ternary | AI (phantom-deps): @jsep-plugin/ternary declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:async-mutex | AI (phantom-deps): async-mutex declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash declared in dependencies; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): moment declared in dependencies; phantom-dep heuristic false positive. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 2.3.16 | 24 / 27 | |
| 2.3.15 | 24 / 27 | |
| 2.3.14 | 24 / 27 | |
| 2.3.13 | 24 / 27 | |
| 2.3.12 | 24 / 27 | |
| 2.3.11 | 24 / 27 | |
| 2.3.10 | 24 / 27 | |
| 2.3.9 | 24 / 27 | |
| 2.3.8 | 24 / 27 | |
| 2.3.7 | 24 / 27 | |
| 2.3.6 | 24 / 27 | |
| 2.3.5 | 24 / 27 | |
| 2.3.4 | 24 / 27 | |
| 2.3.3 | 24 / 30 | |
| 2.3.2 | 24 / 30 | |
| 2.3.1 | 24 / 30 | |
| 2.3.0 | 24 / 30 | |
| 2.2.7 | 24 / 30 | |
| 2.2.4 | 24 / 30 |
v2.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.