@decaf-ts/transactional-decorators No license 27 versions

@decaf-ts/transactional-decorators

npm Repository Homepage

27

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

tvenceslauvnogueira91pccostadcardosopdmfcdemersoncarvalho

Keywords

transactionslockingdecoratorsconcurrencydecaftypescriptsynchronizationconsistencydatabasepessimistic

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@decaf-ts/decorator-validation	AI (phantom-deps): Same org scope; likely a transitive/peer dep not directly imported in this package.	ai	2026/05/04
phantom-deps	phantom-dep:@decaf-ts/injectable-decorators	AI (phantom-deps): Same org scope; likely a transitive/peer dep not directly imported in this package.	ai	2026/05/04
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get used in a Proxy trap to conditionally suppress log calls — standard TypeScript decorator/proxy pattern, not obfuscation.	ai	2026/05/04

Versions (showing 27 of 27)

Version	Deps	Published
0.12.0	4 / 3	2026-06-04
0.11.0	4 / 3	2026-05-10
0.10.0	4 / 3	2026-05-10
0.9.0	4 / 3	2026-05-10
0.8.0	4 / 3	2026-05-09
0.7.0	4 / 3	2026-05-09
0.6.0	4 / 3	2026-05-09
0.5.0	4 / 3	2026-05-09
0.4.5	4 / 3	2026-05-09
0.4.4	4 / 3	2026-05-09
0.4.3	4 / 3	2026-05-07
0.4.2	4 / 3	2026-05-07
0.4.1	4 / 3	2026-05-07
0.4.0	4 / 3	2026-05-07
0.3.9	4 / 3	2026-03-20
0.3.4	4 / 2	2026-01-21
0.3.2	4 / 2	2025-12-24
0.3.1	4 / 2	2025-11-25
0.3.0	4 / 2	2025-11-20
0.2.2	4 / 2	2025-11-07
0.2.1	4 / 2	2025-11-07
0.2.0	0 / 2	2025-11-07
0.1.5	0 / 2	2025-11-05
0.1.4	0 / 27	2025-10-27
0.1.3	0 / 31	2025-07-13
0.1.2	0 / 31	2025-05-27
0.1.1	0 / 31	2025-05-27

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.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.

v0.1.5

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.4

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.3

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