@supernova-studio/pulsar-language No license 22 versions

@supernova-studio/pulsar-language

npm Repository Homepage

22

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

artufimtcevoskar_koristkasupernova-cijiritrecaksusergiiseva-supernovamatej.bobeksn-filipdanisko

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Internal/proprietary package; sparse README and no keywords are expected for this type of package.	ai	2026/05/30
phantom-deps	phantom-dep:abab	AI (phantom-deps): Referenced in config files only, not a real import concern for this package.	ai	2026/05/20
phantom-deps	phantom-dep:dot-prop	AI (phantom-deps): Referenced in config files only, not a real import concern for this package.	ai	2026/05/20

Versions (showing 22 of 22)

Version	Deps	Published
2.7.21	15 / 26	2026-05-18
2.7.20	15 / 26	2026-05-15
2.7.17	15 / 26	2026-03-26
2.7.15	15 / 26	2026-03-20
2.7.14	15 / 26	2026-03-19
2.7.10	15 / 26	2026-01-30
2.7.9	15 / 26	2026-01-05
2.7.5	15 / 26	2025-11-14
2.6.32	15 / 26	2025-06-12
2.6.29	15 / 26	2025-06-02
2.6.27	15 / 26	2025-05-30
2.6.25	15 / 26	2025-05-28
2.6.24	15 / 26	2025-05-28
2.6.23	15 / 26	2025-05-28
2.6.22	15 / 26	2025-05-28
2.6.21	15 / 26	2025-05-28
2.6.20	15 / 26	2025-05-23
2.6.19	15 / 26	2025-05-23
2.6.18	15 / 26	2025-05-23
2.6.17	15 / 26	2025-05-21
2.6.16	15 / 26	2025-05-21
2.6.15	15 / 26	2025-05-20

v2.7.21

1 finding

LOW No provenance attestation provenance

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

v2.7.20

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.

v2.7.17

1 finding

LOW No provenance attestation provenance

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

v2.7.15

1 finding

LOW No provenance attestation provenance

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

v2.7.14

1 finding

LOW No provenance attestation provenance

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

v2.7.10

1 finding

LOW No provenance attestation provenance

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

v2.7.9

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.

v2.7.5

1 finding

LOW No provenance attestation provenance

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

v2.6.32

1 finding

LOW No provenance attestation provenance

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

v2.6.29

1 finding

LOW No provenance attestation provenance

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

v2.6.27

1 finding

LOW No provenance attestation provenance

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

v2.6.25

1 finding

LOW No provenance attestation provenance

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

v2.6.24

1 finding

LOW No provenance attestation provenance

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

v2.6.23

1 finding

LOW No provenance attestation provenance

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

v2.6.22

1 finding

LOW No provenance attestation provenance

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

v2.6.21

1 finding

LOW No provenance attestation provenance

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

v2.6.20

1 finding

LOW No provenance attestation provenance

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

v2.6.19

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.

v2.6.18

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.

v2.6.17

1 finding

LOW No provenance attestation provenance

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

v2.6.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.

v2.6.15

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.